Rearranged windows & forgotten layout after wake from sleep about fancywm

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[veselink1]

Can you please attach the log file as well. I'm not sure why you're seeing what you're seeing, but the logs can help explain.

The log file will be fancywm.log in the settings directory.

[tgrosinger]

This issue seems to also occur if you unplug a monitor and plug it back in. Windows positions are not remembered.

[coffeeneed]

This unfortunately happens to me too. My log files tells me nothing:

2024-05-26 09:27:33.755 +02:00 [WRN] FancyWM v2.12.1.1 (https://www.microsoft.com/store/apps/9P1741LKHQS9) on Microsoft Windows NT 10.0.22631.0
2024-05-26 09:27:34.803 +02:00 [WRN] Using the multi-monitor tiling backend

[veselink1]

Thanks @coffeeneed. I suspect this is related to OS seeing that the monitor is being switched off and on, in which case the window state will be cleared.

I cannot think of a clear mitigation - a user might genuinely unplug a monitor, and in that case, windows will be moved to the visible area. Perhaps we can retain the layout in case of 0 monitors connected, but will need more info to know for sure.

I could add some extra logging around that area of the code, and with the help of a volunteer, capture logs to use to create a possible fix.

[coffeeneed]

@veselink1 Thank you for the follow-up. I've done some research and basically concluded the same as you. I also understood that, in some circumstances, this behavior could manifest differently on DP vs. HDMI. However, this hasn't been tested from my part.

I'm talking way out of me league here, but aren't there any way in the Windows API to check for monitor or hybernation wake-ups (what ever)? If that's the case, why couldn't you listen for change in that and automatically rearrange the Windows back to its position -- which is derived from the last stored information of such data?

Again, there's probably a reason this hasn't been done already, so please forgive me for being "Captain Obvious" here.