2016-01-27, 14:18
(2016-01-27, 00:43)marcelveldt Wrote:(2016-01-26, 22:52)Jayz2K Wrote: Interrested in this too !!!
I have 3 custom files I don't want to be overwritten at skin update so thinking about to just provide them for copy in 16x9 folder and remove them from the package. This could avoid user to manually override them at each version bump.
So if I can make a suggestion, a skin.string is more reliable for a check because kept in skin settings.
Otherwise you will get a fail at reloadskin ?
https://github.com/marcelveldt/script.sk...ile-exists
Thanks Will test ...
Coming back to the Skin.String through DialogSelect, is it possible to resolve $LOCALIZE[] as value before writing it ? I localized all my values because when there's only 2 option, I keep using onclick to minimize the click amount.
Also, what the "Description" argument is intended for ? Is it just for Skinner infos and can it used as a property or something in DialogSelect.xml ?
Thanks
EDIT : Forget that, just realized when a string is written in a language, it will break everything if switching to another :/
The only solution is to use your .label prefix, but wanted to keep things simple if only two options (easier to just click to switch than click to open, click down to hilight, click to select). Maybe using an additional argument to skip the DialogSelect and go directly to the next (will then need an additional ordering ID ?).
Not that much important though ...