Alright, the .ini itself isn't enough for a clear picture of the code, the Variables.inc should have been included as well, but luckily I still had one of my earlier versions of the skin in my "skin database", and reading a bit through the RainRGB4Readme hopefully made the issue quite obvious. The thing is, my previous advice about removing the FileName parameter from the context menu bang above was wrong, because apparently RainRGB4 requires both the VarName and the FileName parameters, as it changes the said variable in the specified file (hence why I said earlier that I wasn't 100% sure of what RainRGB expected). That means you can't achieve what you want by manipulating those parameters, because RainRGB will always write the last changed value of the variable in the Variables.inc file. However, a simpler alternative of "overriding" (but not "overwriting") that value right after Rainmeter reads the .inc should work. Something like:
in the .ini file you posted would normally override whatever font color is read from Variables.inc when parsing the following line (aka last line in the code snippet above). This should set the color to the above at skin load, regardless of what other value for the color was written by RainRGB in the Variables.inc file when you change colors. No change is needed to the context menu action from the .ini file, so keep it as it is.
Code: Select all
[Variables] ; Include weather settings and language variables @Include1=#@#WeatherComJSONVariables.inc @Include2=#@#WeatherComJSONMeasures.inc @Include3=#@#Variables.inc FontColor=5,150,255
Let us know if this works!
P.S. If by any chance you want to also overwrite the value written by RainRGB in Variables.inc with the one above, you can add something like as the first bang in the OnRefreshAction option from the [Rainmeter] section in the .ini file. This will work because the OnRefreshAction is executed after the first skin update, and by that time the variable is already initialized with the desired value.