- Nov 22, 2024
-
-
-
-
-
-
-
-
-
This adds a todo_wine because it exhibits a FVWM bug: the window manager doesn't keep the _NET_WM_STATE maximized bits, and instead simply resize the windows. The missing events don't matter too much, although they would prevent us from serializing the updates with other changes, but it also makes it impossible to figure whether the windows are actually maximized or not. For visible windows, the message we send to the window manager simply doesn't trigger any PropertyNotify event. The update is considered as pending until the maximized style is cleared, and we never try to remove the maximized state from the Win32 state. For hidden windows, the _NET_WM_STATE property is changed directly, this sticks and we receive a corresponding PropertyNotify event. However, as soon as the window is mapped, FVWM removes the bits and we receive another PropertyNotify event accordingly. This can only be considered as a genuine state update, and we clear the maximized state from the Win32 side accordingly. Previously, as the state updates were not re-entrant, the update didn't trigger another window manager state/config update and the window stayed in an inconsistent state, which somehow passed the tests. As the updates are now re-entrant, the window manager is notified of the maximized state removal, and resizes the window to its normal size, then fails the tests.
-
-
It sometimes create a feedback loop, trying to override the window manager config changes.
-
In order to better distinguish them from the ConfigureNotify events sent by the WM. Some window managers (openbox) send a sequence of ConfigureNotify to top-level window frames when restoring them from minimized state, for animation purposes, and they shouldn't be reflected on the Win32 side. We do not need to update the Win32 state when top-level windows frame is being moved, as the WM will send us a ConfigureNotify later and we only need to keep track of its position for mouse event coordinates. Handle the generated GravityNotify events for embedded windows only, to match their Win32 state/config with their X state/config.
-
-
-
-
-
-
Fixes NtUserGetWinMonitorDpi always returning the primary monitor DPI.
-
-
-
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
Use it to reimplement NtUserFindWindowEx().
- Nov 21, 2024
-
-
Signed-off-by:
Gabriel Ivăncescu <gabrielopcode@gmail.com>
-
-
-
Fixes regression by 9d34c44d. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=57325
-
-
-
-
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com>
-
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com>
-
-
-
-