Rainmeter Forums

When rmskin file is on other partition than rainmeter and you try to install skin, skin won't install correctly. SkinInstaller will create folder #PROGRAMPATH#Skins in folder with selected rmskin file.

Rainmeter is used as portable version.

Edit:
It won't work if SkinPath=#PROGRAMPATH#Skins\ is used.

I don't understand what you are saying.

Use About / Version and "Copy" the values and paste them here.

I mean SkinInstaller.exe doesn't support built-in variables

4.2.0 r3111 64-bit (Jul 8 2018) - English (1033)
Windows 10 Home 1803 64-bit (build 17134) - English (1033)
Path: R:\Rainmeter\
SkinPath: R:\Rainmeter\Skins\
SettingsPath: R:\Rainmeter\
IniFile: R:\Rainmeter\Rainmeter.ini

oZone wrote:I mean SkinInstaller.exe doesn't support built-in variables

No, it certainly does not. Those are only valid in the context of a running skin.

I still don't understand the issue at all..

With your setup, SkinInstaller will install skins to R:\Rainmeter\Skins\.

What are you asking? There are no "settings" or command line options for SkinInstaller that tells it where the path to your skins is, that is automatic. Since Rainmeter doesn't even have to running at all to use SkinInstaller, it figures it out by first looking in the same folder that it is in itself, (presumably your program path) and if Rainmeter.ini is found there, it reads that to determine the path to the skins. If not, then it goes to your AppData\Rainmeter\ folder, and looks for Rainmeter.ini there and reads it.

You can't use variables of any kind in Rainmeter.ini, that isn't a skin, and doesn't understand variables. Rainmeter.ini isn't a skin and isn't "run" inside of Rainmeter, it can't know anything about variables.

jsmorley wrote:No, it certainly does not. Those are only valid in the context of a running skin.

I still don't understand the issue at all..

With your setup, SkinInstaller will install skins to R:\Rainmeter\Skins\.

I thought that you can use built-in variables in rainmeter.ini, because ConfigEditor= works.
But if you use them in SkinPath= it won't work.

oZone wrote:I thought that you can use built-in variables in rainmeter.ini, because ConfigEditor= works.
But if you use them in SkinPath= it won't work.

It doesn't work with ConfigEditor either... If you are using a #Variable# there in Rainmeter.ini, it is failing, ignoring the option entirely, and just using whatever you have defined to edit .ini files in Windows.

jsmorley wrote:It doesn't work with ConfigEditor either... If you are using a #Variable# there in Rainmeter.ini, it is failing, ignoring the option entirely, and just using whatever you have defined to edit .ini files in Windows.

I don't know but I use ConfigEditor with #PROGRAMPATH# and it works

oZone wrote:I don't know but I use ConfigEditor with #PROGRAMDRIVE# and it works

No, it doesn't...

jsmorley wrote:No, it doesn't...

I have this
ConfigEditor=#PROGRAMPATH#..\Notepad++Portable\Notepad++Portable.exe
When right click on skin and choose Edit skin it will open notepad++

Edit:
Same with ConfigEditor=#PROGRAMDRIVE#\Notepad++Portable\Notepad++Portable.exe

You are being tricked...

What is happening is that the #PROGRAMPATH# is being ignored, and you end up with

ConfigEditor=..\Notepad++Portable\Notepad++Portable.exe

Since ConfigEditor can use relative paths in its definition:

Defines the path to the text editor used to edit Rainmeter's configuration files when "Edit Skin" or "Edit Settings" is chosen from the context menu or Manage. Relative paths can be used here, which may be useful for portable installs.

That is the same thing, so it works fine.