moshi wrote:
it will affect them again as soon as the download one of my skins that come with the old version. :/
during install of a skin there is no way to tell whether a plugin that comes with the skin is older or newer than the currently installed one.
i'll update my skins but that will take a while.
One thing a user can do, but it's not going to be something intuitive to anyone, and would be something you would just have to tell them to do is:
Copy a "new" version of the RunCommand.dll file from %APPDATA%\Rainmeter\Plugins and put it in Program Files\Rainmeter\Plugins.
Rainmeter will "prefer" a copy of a plugin .dll that is in Program Files over one in %APPDATA%, in effect prefer a "built-in" plugin over a "3rd-party" plugin of the same name.
Since all .rmskins will install any copy of the .dll they contain to %APPDATA%, they can then avoid overwriting a new one with an old one, without having to be super-careful when they install skins to watch for and uncheck the "replace" box during the install.
The good thing here is that I really believe that a very small percentage of folks are going to have any problem with the old version. The vast majority of people are already going to have VS2012 on their systems, either from other software, or from an older version of Rainmeter itself.
The bad thing is that until and unless we get RunCommand into the Rainmeter "build", so it is distributed with Rainmeter, this can and will crop off from time to time when older skins are installed.
I am very uneasy about this. Not so much about RunCommand in particular, but the entire issue as it relates to 3rd-party plugins. This is very poorly thought through right now, mostly due to the fact that for a long time, there just were no 3rd-party plugins to speak of. However it seems to be taking off a bit, and this "version" issue is going to bite us in the butt, sooner as likely as later.