2014-06-25, 16:49
I'm currently using it same way how you described and have list completely unrelated to Home screen and its menu and it's working fine. But from generated include file and brief look into code I thought that mainmenuID is mandatory. If not then it's better for me .
About widgets, in my use-case I have custom Video hub window with list (filled by script) and up to 3 widgets. If I remember correctly (not at home now, so can't check it) widget property is filled to list items, but in my case I want to show same widget(s) aside from position in list. I can hardcode widgets to look for property at specific index but it'll make user configuration mess and can possibly cause problem with lists shorter than 3 items. I guess your approach is based on mainmenu + 1 widget per menu on Home screen point of view where it's logical, but it's bit limiting for other use-cases. My idea was to have possibility to save widget properties directly to Home window like script.skinshortcuts.[widgetID].widget or something similar. But maybe I'm over thinking things and there is some easy solution already available
About widgets, in my use-case I have custom Video hub window with list (filled by script) and up to 3 widgets. If I remember correctly (not at home now, so can't check it) widget property is filled to list items, but in my case I want to show same widget(s) aside from position in list. I can hardcode widgets to look for property at specific index but it'll make user configuration mess and can possibly cause problem with lists shorter than 3 items. I guess your approach is based on mainmenu + 1 widget per menu on Home screen point of view where it's logical, but it's bit limiting for other use-cases. My idea was to have possibility to save widget properties directly to Home window like script.skinshortcuts.[widgetID].widget or something similar. But maybe I'm over thinking things and there is some easy solution already available