8 May
2025
8 May
'25
4 p.m.
Thanks. In that case it seems like the prudent thing to do would in fact be to call Reset() from WM_WINDOWPOSCHANGED, as the application does, and probably also test that we did so at most twice? I imagine we might have been afraid to do so lest a failing test result in a hang or crash rather than a simple "test failed" message, but I at least am of the school of thought that a failing test is a failing test, regardless of the mode of failure. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7968#note_102834