(2015-10-01, 10:02)jurialmunkey Wrote: As long as it is only for the new 312 way of setting widgets, then I think that would be the best approach. I imagine that many skins using the old way of setting widgets would be using VARs to set the widget title, so any change to the label wouldn't be reflected anyway which would cause some confusion to end users (just thinking about how Arctic is currently set-up, though I will be migrating to the new way).
Thanks for the feedback
The script has no responsibility for the widget title with the old method, so yes, it would be for 312 only
(2015-10-01, 13:04)finalmakerr Wrote: 1.
Is it possible to use overrides.xml for the thumb section? For example:
<thumb labelID="pictures">icons/pictures2.png</thumb>
The <thumb /> is empty in script-skinshortcuts-includes.xml. I tried to use the overrides.xml in order to fill it up but it's not working. For the <icon> part it's worked!
That's way i can use two different icons for a specific condition.
No, it's not possible for the skin to set the thumb, only the icon. This is done for various reasons, not least so that the user choice of image (which get's set to thumb) is always the one that's used.
You can, though, add an additional property which you can use as your focused/unfocused item (though letting the user browse for an image requires the repo version). See the docs I linked to above.
(2015-10-01, 13:04)finalmakerr Wrote: 2. Is it possible to use only the actions part in script-skinshortcuts.xml? For example:
Selecting specific button in SkinSettings.xml then:
Code:
RunScript(script.skinshortcuts,type=manage&group=mainmenu)
I have my own customized window which is looking exactly like my home window.
There i can simply edit any button with a click. Now the list of available options i have is quite nice but not great as what this addon can provide, so i tried to use my own customized window and trigger the actions such as Move and Action directly in my action window but i can't seem to find any direct command for doing that.
So far it's seem like this is the only way to manage the buttons:
Code:
RunScript(script.skinshortcuts,type=manage&group=mainmenu)
I used the globaloverride like that:
Code:
<override action="globaloverride" group="mainmenu">
<condition>Window.IsVisible(SkinSettings.xml)</condition>
<action>RunScript(script.skinshortcuts,type=manage&group=mainmenu)</action>
</override>
Now if i could only use that globaloverride and tell it the specific button i want to change, then i would want to edit the script-skinshortcuts.xml and keep just the actions menu.
Another issue is that there is only down/up movement but i actually use 4 directions..
The closest the script has in the 'Just Select' method which just lets the user select a shortcut and pass that information to the skin to manage, though it's completely separate from the menu management features of Skin Shortcuts. There's no way to launch the management dialog for setting the properties of a single shortcut.
It's broadly possible (though I've never seen it done) to skin script-skinshortcuts.xml to look like the homepage, but that is likely very difficult to achieve well. The closest to a move left/move right would be a button which sends multiple clicks to the up/down buttons so that the item is in the correct position in the correct column (that assumes that the menu is displayed in a panel control.)
It's likely what you want to do is quite doable with minimal changes to the script - passing in the position of the selected item when calling manage, then having the script focus list 211 (which could be hidden offscreen somewhere) on that shortcut. I don't have time at the moment to make the changes though, but patches are very welcome!
(And even if that was done, due to how and when the changes are saved, it probably wouldn't work well if you're using the script to manage the position of menu items, and could be difficult with hidden items in the list...)
The global override doesn't do what you think
It's not useful for letting the user choose a shortcut, but rather for the skinner to identify that, in certain situations (say when they want the first click on a menu item to show the submenu), a different action to that which the user has selected should be used.