It appears that the new skin packager/installer/ .rmskin format do not honor a custom SkinPath setting in Rainmeter.ini.
Installation and version data:
I noticed the problem when I was packing up my Elementary skins for the new 2.3 format.About Rainmeter wrote:2.3.0 r1497 64-bit (Jun 25 2012)
Path: C:\Program Files\Rainmeter\
IniFile: C:\Users\Matthew\AppData\Roaming\Rainmeter\Rainmeter.ini
SkinPath: C:\Users\Matthew\Rainmeter\
As you can see, in the skin packager when one selects "Add Skin," the packager does not correctly enumerate already installed skins:
That's okay I suppose, because I can just use "Add a custom folder." So I proceeded to pack up my skin. (Here's the .rmskin: https://www.cubby.com/p/85f63274bd8348b18c2c430306bbffc5/Elementary_1.5.rmskin)
However, when I test the .rmskin, the installer does not detect that the skin is already installed:
And if I run the installer, I get the skin dumped into my Windows User folder, in a folder named "Rainmeter(SkinName)":
(Tested with Elementary and with JSMorley's InterfaceLIFTer skin)
A bit of a bummer, that. Besides putting my skins back into the default location, is there any way I can mitigate the issue? (I mean, I can install manually, but that's no fun. )
And even though they are bugged on my system, should .rmskins I create still work fine for people with default installations?
Thanks, and have a nice day.
-fh