Thanks for your responses.
I suggested that it could be possible to add some windows event listener in the Rainmeter code, which will trigger the widget update whenever it receives system event of changing display configuration. For example, it could listen to WM_DISPLAYCHANGE messages, and trigger refreshing on receiving such message. But of course, I don't know if it could be implemented in Rainmeter this way.While I agree with your stance since I also need to "manually" refresh all skins to restore my desktop work area settings, this behavior has a reason. Refreshing all skins can be a resource intensive operation given that all skin folders are re-read from the disk in that moment.
That being said, when changes in the screen properties occur, some messages are written and displayed in the About > Log tab, so one way of dealing with this and automatically refresh all skins would be to enable writing the log to a file, use a WebParser measure to parse that log file from the skin, then, when such a message occurs as the last line in the log, execute a !RefreshApp bang to refresh all skins:
https://docs.rainmeter.net/manual/bangs/#RefreshApp
That's a great workaround, thanks for the suggestion! I guess I will stick to it for now.Another way is making sure your skins have main monitor selected for their position and disable "keep on screen".
Statistics: Posted by emvaized — Today, 8:29 am