(2016-02-29, 22:36)tomer953 Wrote: [ -> ]it become a new trend, making those categorize, like "Kids", "sport", "VOD" etc.. sub-menus are old-fashion now, and users prefer custom windows with their "sub-menus" instead.
IIRC, library nodes don't let you access for add-ons, so you can't create fully customizable nodes as the users are often does.
Sure they do
http://forum.kodi.tv/showthread.php?tid=...pid2232211
(2016-02-29, 22:36)tomer953 Wrote: [ -> ]Super favorites and advanced launcher are fine, but I'm still thinking that implement categorize in skinshortcuts will be much more easier for skinners and users to use.
and to be honest, i'm not going to add a new dependency for my skin to advanced launcher, I don't see it as "a must have" addon.
with that being said, I just suggested it as a new feature, and wanted to share that thought with you.
"no" is certainly a legitimate answer.
thanks anyway.
Adding specific support is a 'No' from me - though it's an open source script, so if someone does want to take it on they are more than welcome.
However, Skin Shortcuts may get you a lot of the way already with a lot of creating skinning.
For example, add the following to your overrides
Code:
<groupoverride group="mainmenu">SetProperty(Container(9000).ListItem.Property(submenuVisibility),Home)</groupoverride>
then, when your new window is launched set the content of the list to
Code:
<content>skinshortcuts-group-$INFO[Window(Home).Property(submenuVisibility)-1</content>
To have the first additional submenu shown.
Or get really creative and use custom properties of the main menu item (widget, for example) to customise your additional window. Build them with templates but pull out the submenuVisibility into a property
Code:
<property name="submenuVisibility" tag="property" attribute="name|submenuVisibility" />
use it in the visibility condition for your controls
Code:
<visible>StringCompare(Window(Home).Property(submenuVisibility),$SKINSHORTCUTS[submenuVisibility])</visible>
and include your template in your custom window, and the possibilities become much larger! (And double-check all my code - I've not actually checked any of this!)
Edit:- Though one I do know, because I added it to my own Conq mod the other day, is that it's even possible to do something like this:-
Code:
<property name="path">$INCLUDE[skinshortcuts-group-$SKINSHORTCUTS[submenuVisibility]]</property>
and within your controls
Code:
<content>$SKINSHORTCUTS[path]</content>