@
curael @
Guilouz - unfortunately, checking against ListItem.DBType won't work because I need to use includes and ListItem infolabels are filled
after include conditions are evaluated. The best workaround I've come up with is adding a check against the
filename of the smart playlist. So if the smart playlist filename ends in Genres.xsp, then it will be treated as a genres widget (likewise, if it ends in Studios.xsp, Countries.xsp, Directors.xsp, Years.xsp, or Tags.xsp it will be treated accordingly). So if you save your playlist as AnimeGenres.xsp then the skin will treat it like a genre widget (you can name the actual widget whatever you want, just the playlist filename needs to be named as such). On latest git.
EDIT: Also just made a change where the aspect will show "Genres" if it is a genres widget (or "Studios" for studios, or "Text" for years/tags/countries/directors).
Btw, @
curael I've discussed widget sizing many times previously. All widgets have the same height - the difference between "square" and "poster" is that poster will force the artwork to be stretched to the whole box, whereas square will only use the top 2/3 of the box for artwork (see music album widgets for example). Hopefully this will make it clear when a genre widget is set.
The height restriction is to ensure proper alignment of widgets - it gets much trickier to have the scrolling alignment work properly when the widgets are different sizes. You will notice that, unlike in Estuary, Aura keeps the widgets centred on screen when scrolling up and down. Centring the widgets allows you to clearly see what the previous and next widgets will be, whilst also giving a clear indication that you can scroll up/down and making it obvious when you reach the end of the widgets. (This is also why the categories widget can only be in the first slot, because that way, having different sized widgets doesn't mess-up the alignment when scrolling).