Care to explain a bit more?
It would tell me that (image) menu_on.skin which cause me to look for it only to find it was just misspelled (mennu_on.skin). Sometimes the graphic was missing all together.
External_GPS.skin was always missing the underscore!
All this cause me to scratch my head wondering what was wrong :confused: - until i ran skinchecker! :dance:
With this version i hope to trim a lot of fat (unnecessary files and images) in some skins.
Well most skins will 'work' as long as they have a general.ini and menu.skin, anything is just a matter of some screens not working.
Now if you want to check whether RoadRunner will actually start those are all you need to check for.
However parsing the whole skin and then saying it won't work just because the odd jpg or png is missing will probably mean none of the skins out there 'work'.
However if you want to tell me what sort of reponses you would want if your config called the skinchecker I can look at implimenting that for you.
1 - Valid
2 - Invalid
3 - Working, but bad
The third state can mean a lot more to skins developers, and that's the motivation for this skin checker ;)
That's just a matter of what's important in each particular situation
If every single piece of software made for RR can work together, than we will have something like a ant farm, where each ant do it's job to make all the system work together as a live organism ;)
gotta some other ideas... but gotta talk to guino first
believe me when i say that some small coordination can make RR the better (forever FREE) frontend EVER
Great, now we're being compared to ants?? LOL
I think that would work, and just calling the skinchecker with a param of the skinpath to check. Maybe have 2 valid states, one thats used for non png'ed skins and the other with, so I could make sure that if a png skin is selected then make sure that fastmode is using gdi+. Just trying to elminate less questions like "I just installed this skin, and now all I get is.....how do I fix it?"
It would really be nice if we did have some storta standard, like all plugin's in the plugins folder, that would have made it real easy to also be able to config the plugins right from the config as well, but there is no standard so when people do make a plugin they just have you put it in what ever folder instead of having everything in one place. just like WA, every plugin that you add all go's into the plugin folder, duh...
Hmm, png or no png, that would be easy, however deciding on which png makes it a png dedicated one. What if someone had pngs in there for another reason?
One question is, what difference does it make if you run a non transparent skin in the fastmode that is for Transparent ones?
Its a one way street, you can use non transparent(jpg) skins in what ever mode you want, but you can not do the same with the png's, which is where the user questions come from like in the above post. As there are those users that don't like to read and then post about a prob b/c they don't know what is the correct setting(s) to use with what they "think" the prob is... this is hopefully where my config would catch it before hand and help to get things set correctly so the user can continue with the next problem, whatever that might be...
So maybe the default should be to use the new fastmode then.
Unless there is a disadvantage to using it when not using pngs?
Just like the default for gestures should be off ;)