(2013-10-18 13:25)Kode Wrote: we dont have
In skin language it would be the same as you can't use variables, thus 1st example differs only in that it's item has a longer string.
Quote:if we had $INFO[Window(Home).Property(Plexbmc.LatestMovie.UUID.1.Title)]
then we would only have 25 items, because plexbmc only creates 25 items within Plexbmc.LatestMovie.UUID
This is true for a section (25 limit) but the loop goes on until number of sections is exhausted and populates properties further with a different UUID, of course.
Quote:so in effect with 4 sections, we would have 4 lists of 25 items, rather than the current 1 list of 100 items. look at it like this:
We have 4 list with 25 items NOW, but as I have to use fixed number of slots (50, until I raised it to 60), our list of 100 gets cropped. I have no way of picking up first or third 25 from the list of 100, nor do I have a means to assign one list of the 4 available dynamically to a list. If you create 4 sets of items, each containing 25 items, I would need to prepare 4 lists for them.
Quote:And because you are listing all the Plexbmc.LatestMovie.aaaa-aaaa-aaaa-aaaa items you dont have to check if the uuid is correct because it wouldnt be listed if it wasn't
Sure, if we have a list with UUID we can tell it to show up when Main menu item with the same UUID is selected (focused). However, I would need to make several empty lists ready, to make sure every library section has one. Then I don't need to check list items for visibility, only the list itself.
If you can produce skin code with a script, according to a pattern I would provide so I don't do it by hand, we can give it a try.