Good tip. Ill have to remember that. Will fix and re-upload.
Edit: I'm not sure how this would effect the file, Because the file path is #@#Config.exe. There shouldnt be any spaces either way, Right? or does the #@# include the full path to the resources folder? I thought it was more of a shortcut. Can someone clarify?
UnforgivenRevival wrote:I'm not sure how this would effect the file, Because the file path is #@#Config.exe. There shouldnt be any spaces either way, Right? or does the #@# include the full path to the resources folder? I thought it was more of a shortcut. Can someone clarify?
There is a specific order in which Rainmeter "decodes" options in a skin. Variables like #@# are replaced before the option is even interpreted as a bang. So
Rainmeter does not account for the fact that "C:\Users\YourName\Documents\Rainmeter\Skins\RainGas\@Resources\" used to be "#@#", because that replacement is done in a previous "stage." This is actually a good thing, because it gives us much more freedom in using variables to construct a skin however we want. But it does have some counterintuitive consequences, as you have discovered.
(Just to be clear: bangs are typically the only case where spaces are an issue. It's fine in most other contexts, such as ImageName, ScriptFile, etc. But it's important in bangs because they have specific "parameters" that must be separated correctly.)
It's always a good idea to put filepaths in quotes for that reason. There's no downside, after all.
I actually don't have spaces in my Windows username. Could it be an XP-specific thing, since I suppose my path would include the spaces in "Documents and Settings" and "My Documents" (C:\Documents and Settings\Matthew\My Documents\Rainmeter\Skins)?