Cariboudjan wrote: ↑January 24th, 2023, 9:29 pm
SkinWidth= does not use the AutoSelectScreen value when Rainmeter is opened. Only if the skin is later refreshed after open.
This is probably because:
- the [Rainmeter] section not supporting dynamic variables while monitor variables and
AutoSelectScreen require it; the result is the value being static
- if it happens only when Rainmeter is opened at startup, it could be related to not having enough time to initialize stuff, though that's unlikely
- if it happens every time Rainmeter is opened even if not at startup, then it's clear that the -1 aka the primary monitor is still the value of @N
- use DynamicWindowSize=1 and a dynamic Shape or Image meter as a background to set the skin dimensions, to freely use dynamic monitor variables
- use a separate "loader" skin to force a refresh on the main skin after some reasonable delay for loading it
- use the !AutoSelectScreen bang and a refresh once (via some other dynamic variable that triggers and cancels it) in your last meter instead
Note: Testing is required for the above. I would have done it myself if I had multiple monitors, but although my registry seems to disagree, I don't. I might have missed some variations for the said hypothetical workarounds because of that. Also, some variants may only act after the first refresh / update happens in the main skin, so for a split second the skin could still use the wrong work area before it is "stabilized".