- This topic has 4 replies, 2 voices, and was last updated 13 years, 4 months ago by
.
-
Posts
-
Hi Serge that is fantastic! The “Update All” action replaces 10 skins so fast there is hardly even a flicker, it's 1000 times faster than I can do it and it completely removes the human error element.
Having said that, I did find that 3 of the 11 skins in one app were updated with the wrong skin. For example, a skin called DeepPurple (internal) loaded WMP. I manually deleted/re-added the skins that had problems and from then on everything worked perfectly, including multiple repeats of using 'update all'. I didn't notice that anything had changed about the skins with the reimport (they definitely had the same name and other properties that are visible in the skin manager) so I think it may have been an indexing issue. I haven't tested this fully but I think what happened is that the skin called DeepPurple loaded WMP, WMP loaded Golden, Golden loaded DeepPurple. I can get the old SkinManager that exhibited this behaviour out of the repository if you need something to test this with.
TLDR: If anyone finds that “Update All” loads the wrong skin then they can probably solve it by reimporting the skin manually once, from then on it should work.
Regards,
Hamilton
The problem with the reimport messing up the indexes still occurs, any chance of a fix pls? The messed up indexing doesn't occur all the time but its often enough to negate the usefulness of this handy feature.
If you cannot repro, one thing you might try is to rename one of the skins and then try again. I don't know when this first occurred but at some point DeepPurple became deeppurple and I've had to rename that skin in the skin manager for compatibility with the rest of the program (as unfortunately the skin name appears to be case sensitive). So what might have happened this last time is that it failed to load DeepPurple because the file was called deeppurple and then that in turn may have messed up other skins also? Just guessing..
- You must be logged in to reply to this topic.