2014-07-11, 15:43
Those are for overriding controls in (most likely) skinsettings.xml. Whilst it's prooved far more user-friendly to provide a single link to edit the main menu, and then a control in the script-skinshortcuts.xml file to edit each submenu, it's possible to let the script fill a list in skinsettings.xml with controls to begin editing the main menu, each submenu and to reset all shortcuts with
The <settingslabel /> properties override the labels of those controls, not controls within the management dialog. As I say, though, better these days to use a link to the mainmenu managment dialog, button 405 (and the others when I get them added) in the management dialog, possibly a reset all button and if necessary provide your own title control for the window rather than provide label 500 (though I'll look again at overriding that.)
And, y'know, the skinsettings.xml list was something i was really pleased with at the time I wrote it - it's what I came up with what became the reload property used in library data provider for, to update a script-filled list automatically when the underlying data had changed. What a waste
Code:
<content>plugin://script.skinshortcuts?type=settings&property=$INFO[Window(10000).Property("skinshortcuts")]</content>
The <settingslabel /> properties override the labels of those controls, not controls within the management dialog. As I say, though, better these days to use a link to the mainmenu managment dialog, button 405 (and the others when I get them added) in the management dialog, possibly a reset all button and if necessary provide your own title control for the window rather than provide label 500 (though I'll look again at overriding that.)
And, y'know, the skinsettings.xml list was something i was really pleased with at the time I wrote it - it's what I came up with what became the reload property used in library data provider for, to update a script-filled list automatically when the underlying data had changed. What a waste