they did some updates on the skinning engine this last time, doing the beta testing. so changing or adding some things to the theme engine has always made my skins need re compiled with the new program installed. it does not seem to make any sense to me either, since the theme engine has no need for monkey to be running when we make the skins. but i've had to do that with all my mm 3 skins i've ever made which is why i waited until the mm 3.1 was released as stable. i don't think they update the defaultly installed skins all the time, but if the mess up in the skins is because the program is looking for new codes that were added doing the updating then the older skins don't have that code. and will mess up like the mm 2 skins did when we were converting them and they did not have all the codes for mm 3. that is the only thing i can find that might cause trouble with the non updated skins being used.pbparker wrote:It does come and go based on the skin being used, but I believe Blue Glass comes with the base MM install correct?
Personally, I can live with the glitch because I like this skin over others. However, I ponder why a skin that comes with MM is somehow broken by a change made in the late 3.1 betas. That or if someone could clarify why these are breaking so we could go in and fix the skins would be most helpful.
Either way, I'll live with it if there's no solution.
but as nohitter151 said it is a program error on the vistas and windows 7. but why it seems to be a skin error on xp pro sp3 is beyond me?
