Ok, I think I have sorted out most of these issues....however, there is at least one issue with your test skin that I did not notice at first.
That issue is most bangs do not accept a File parameter. See !SetOption and !DeactivateConfig (I will talk about this one later). Extra parameters are either ignored or the bang won't work properly (depends on the bang). So in the test skin, these bangs are behaving appropriately since they are ignoring the extra parameter provided.
Outside of that issue, I changed some of the logging messages that *should* help to clarify what the error is. First, I added a check to see if the actual config (and file, if the bang accepts it) exists physically on the disk. There is also a check to see if the config/file exists but it not available to Rainmeter (like if a file is created while Rainmeter is running) in some cases.
The only other issue that I can see involves the !ToggleConfig bang.
First, the documentation is incorrect. Only the Config parameter is required, File is optional. Not sure if that changed at some point (I don't think it did), or if it was just an oversight when creating the docs. We will fix this when a new release comes out.
Second, the underlying code for this bang is really similar to the !ActivateConfig and !DeactivateConfig bangs. To activate a skin, the !ToggleConfig can accept a config and a file - but to deactivate, only the config is needed. So, when the File parameter is provided (but that file doesn't physically exist on the disk), the parameter is ONLY evaluated during the activation code, not the deactivation code. I am not sure what can be done except maybe some documentation on this edge case.
-Brian
That issue is most bangs do not accept a File parameter. See !SetOption and !DeactivateConfig (I will talk about this one later). Extra parameters are either ignored or the bang won't work properly (depends on the bang). So in the test skin, these bangs are behaving appropriately since they are ignoring the extra parameter provided.
Outside of that issue, I changed some of the logging messages that *should* help to clarify what the error is. First, I added a check to see if the actual config (and file, if the bang accepts it) exists physically on the disk. There is also a check to see if the config/file exists but it not available to Rainmeter (like if a file is created while Rainmeter is running) in some cases.
The only other issue that I can see involves the !ToggleConfig bang.
First, the documentation is incorrect. Only the Config parameter is required, File is optional. Not sure if that changed at some point (I don't think it did), or if it was just an oversight when creating the docs. We will fix this when a new release comes out.
Second, the underlying code for this bang is really similar to the !ActivateConfig and !DeactivateConfig bangs. To activate a skin, the !ToggleConfig can accept a config and a file - but to deactivate, only the config is needed. So, when the File parameter is provided (but that file doesn't physically exist on the disk), the parameter is ONLY evaluated during the activation code, not the deactivation code. I am not sure what can be done except maybe some documentation on this edge case.
-Brian
Statistics: Posted by Brian — Yesterday, 11:49 pm — Replies 8 — Views 7169