So, a long time ago I attempted: http://www.mediamonkey.com/forum/viewto ... 04#p239304 and ran into to some problems so frustrating I ended up despising MM so much that I almost went back to iTunes *gasp!*. Well I'm back now and hoped to finish the work I had started and sure enough I'm running into similar problems if i remember correctly. This time I may have found a reason for the erratic behavior though.
Basically, I was editing some Color attributes of the ListBox/Frame/Client ( the element i was working on is irrelavent but anyways ) and now media monkey is no longer accepting changes to the skin anymore. I can change the value in the theme editor and save the Theme.mskn and all but the program itself when I toggle skins, restart media monkey, and even restart the computer still shows the original color.
Now, I had the folder containing my working skin in the C/Program(x86)/MediaMonkey/Skins/ directory and at first I thought it was not getting updated due to some read/write permissions and you may be thinking this is odd because I had been editing and updating by skin toggle all along and didn't have any issue before so why now? So then I thought ok, I'll pull the folders out edit them on my unprotected drive space and then copy them back over. This is the part that is killing me. When I cut the folders out of the skins/ directory MediaMonkey is still seeing the one called DarkGlided that I had been working on even though it's not there anymore. And even weirder, the color that I had messed with some how transfered to all the other skins that aren't even unzipped. I believe this is why the color isn't changing because media monkey is reading some old cached version that isn't the true up-to-date version. It's like that color is in some memory and it's over riding the skins parameters. I actually restarted my compture a second time thinking maybe if it clears the RAM out extra good no crap could be left over and it turns after switching skins like 5 times the color finally got flushed out of the default skins in the skins/ directory but it still remains on the DarkGlided skin i had been building even though that folder isn't in the Skins/ dir.
I don't know how to recreate this error or to prove it but it's happened to me twice now. I remember it happening last time I tried this and it drove me insane. You basically no longer have control of when elements get updated into the skin mediamonkey is seeing.
The only idea i have is if there is some way to flush all cached data media monkey has. Perhaps it's stored in some temporary file, and I could delete it and the program would just recreate it on startup, similar to cookies in web pages and stuff. Other than that, I don't know how media monkey is still seeing that skin when it shouldn't be looking anywhere but the skins directory.
If you help me fix this it would be greatly appreciated. If other people are having this error and it gets fixed it could mean developing skins just got a hell of a lot easier and people would be more willing to invest time. I mean I really think I have a good looking skin and it's a shame for it to die just as it did before to a silly error like this.
I'm begging the gurus of media monkey to save me
UPDATE: even more weird behavior. I went switching the skins around again and I went from VitreousBlue back to the mysterious "DarkGlided" that I removed from the directory and some how the music player looks like part of an iTunes skin which I don't have downloaded and didn't even know existed on my computer... WTF, i'm going crazy. I thought only default skins were Glided, BlueGlass, and VitreousBlue?
"Right Click > Open in new tab" OR "Right Click > Save Image As" and view locally to see whole thing
