On Wed Aug 23 03:42:21 2023 +0000, Zebediah Figura wrote:
Ah, I think that makes sense. So we resize the window from the registry mode to the new mode, but fvwm thinks that the registry mode is still the screen size, notices that the window is maximized with the "wrong" size, and tries to resize it back to the registry mode?
Yes, exactly.
Thinking about it, we might retain approximately as much value by checking for !wm_size_received after reset() returns but before we flush events. I guess what matters to the games is that it doesn't get WM_SIZE or WM_WINDOWPOSCHANGING on the focus window *while* in reset - presumably because it calls reset() from the WM_SIZE message handler, which would cause endless recursion.
Mode changing games would be broken on fvwm regardless of message handling, since fvwm just increases the size to something wrong we'll stretch the output in Present.