This assumes of course that Rainmeter is already running. The !ActivateConfig bang cannot be used as a part of "starting" Rainmeter. ALL "bangs" to Rainmeter.exe, except !LoadLayout, must be used while Rainmeter is running, or the entire command is just ignored. If you are trying to "start" Rainmeter, while forcing it to do something as soon as it starts, you can't do that, other than loading a saved Layout.
MourningStar wrote: ↑August 14th, 2021, 6:51 pm
It is, as stated in the first sentence of post#1.
thx for your help
For your testing, instead of !ActivateConfig try !ToggleConfig to see if it does anything. Is your command-line reporting any errors, or is it just returning without doing anything? Otherwise, I'm fresh out of ideas too. What jsmorley and I posted definitely work.
The 'Toggleconfig' does indeed cause the specified skins to show and hide. However, I believe the command lines as suggested do not allow for variants, as it is requiring the skin's configname (i.e the exact name of the inc). I fear to imagine what adding multiple lines with every variant will result in. Also, if a skin happens to be unloaded at the time the internet Off is executed that skin will load and vice-versa. Not 'precisely' as the op is requesting. If the op faulted in clarity my apologies.
(perhaps if the 'ActivateConfig' parameter worked for me the op would be resolved?)
MourningStar wrote: ↑August 14th, 2021, 9:49 pm
Thx everyone for the help thus far.
The 'Toggleconfig' does indeed cause the specified skins to show and hide. However, I believe the command lines as suggested do not allow for variants, as it is requiring the skin's configname (i.e the exact name of the inc). I fear to imagine what adding multiple lines with every variant will result in. Also, if a skin happens to be unloaded at the time the internet Off is executed that skin will load and vice-versa. Not 'precisely' as the op is requesting. If the op faulted in clarity my apologies.
(perhaps if the 'ActivateConfig' parameter worked for me the op would be resolved?)
thoughts
This is odd. !ActivateConfig only "activates" if the skin is not loaded. If it is already loaded, it does nothing. So it should have worked assuming the skin was unloaded when you tried it. The last parameter of the command line is what you need to activate variants. So, for example:
!ToggleConfig has the same parameters as !ActivateConfig, but will toggle whichever variant needs toggling (you can't activate two of the same variants at the same time).
SilverAzide wrote: ↑August 14th, 2021, 10:07 pm
This is odd. !ActivateConfig only "activates" if the skin is not loaded. If it is already loaded, it does nothing. So it should have worked assuming the skin was unloaded when you tried it.
Ah, correct - that is why nothing happened. Now it work as per these 'conditions'.
SilverAzide wrote: ↑August 14th, 2021, 10:07 pmThe last parameter of the command line is what you need to activate variants. So, for example:
!ToggleConfig has the same parameters as !ActivateConfig, but will toggle whichever variant needs toggling (you can't activate two of the same variants).
Understood - i.e. the variants are 'locked' into this process because of the required 'configname' parameter.
still, not what I'm after. Looking to 'load'/'unload' the specific skin (and the variant on display at the time).
So, not possible to do what I need? If I am not clear perhaps I can re-word the op.