February 2025 - wine-gitlab

[PATCH 0/1] MR7353: winewayland: Implement SetCursorPos via pointer lock.
by Attila Fidan (＠atticf) 18 Feb '25

18 Feb '25

There is no ([not yet?](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requ…) dedicated protocol for requesting pointer warps, but it's possible to request one with `zwp_locked_pointer_v1.set_cursor_position_hint` which may be performed when the pointer is unlocked. The idea is to quickly lock/set position/unlock. This is used by SDL (in some cases: [SDL_MOUSE_EMULATE_WARP_WITH_RELATIVE](https://wiki.libsdl.org/SDL3/SDL_HINT…) and Xwayland. The limitation is/will be that the compositor will ignore requests to warp the pointer outside of surface bounds. What I'd like to have working is the auto cursor placement feature of some applications, where they just want to call SetCursorPos towards specific UI elements inside their single window, and usually they'll be unclipped and have a visible cursor while doing this. This patch also happens to allow mouselook to work in applications which use SetCursorPos for mouselook and aren't getting covered by the heuristics that turn on Wayland relative motion (for some reason the driver thinks the cursor is visible). Seems to affect Half-Life (GoldSrc) on my system. Though force enabling relative motion with an environment variable in a custom build or somehow improving the heuristics will also fix that. A suface/pointer can only have one lock or confinement, and this implementation depends on the pointer lock. So if needed, I temporarily unlock/unconfine in order to do the warp then relock/reconfine. I modified `wayland_pointer_update_constraint` so I don't have to temporarily disable relative motion during this in case it's enabled. I think it's safe/a no-op to attempt pointer warps while using relative motion, as according to the protocol the warp will not generate a relative motion event, and while there will be a wl_pointer motion event, they're ignored while relative motion is being used. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7353

2 1

[PATCH 0/1] MR7352: winewayland: Request warp to win32 position on pointer unlock.
by Attila Fidan (＠atticf) 18 Feb '25

18 Feb '25

If a surface is being clipped and hides the cursor, drawing its own one, winewayland constrains using a pointer lock and enables Wayland relative motion. If the application decides to stop drawing its own cursor and make the cursor visible, winewayland will disable relative motion and pointer lock, and enable pointer confinement. The user will perceive a pointer jump from the win32/application drawn cursor to where the Wayland pointer is after being unlocked and an absolute motion event is received, because they were desynchronized due to the Wayland one being locked in place. The pointer constraints protocol says this: > If the client is drawing its own cursor, it should update the position > hint to the position of its own cursor. A compositor may use this > information to warp the pointer upon unlock in order to avoid pointer > jumps. So, right before unlocking, make a request for the compositor to warp the pointer to the win32 position on pointer unlock. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7352

2 1

[PATCH 0/2] MR7349: win32u, winex11: Sort vulkan devices.
by Paul Gofman (＠gofman) 18 Feb '25

18 Feb '25

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/7349

3 5

Re: [PATCH v16 0/1] MR7322: programs/cmd: Implement ability to abort lengthy directory operations via Ctrl-C. - approved
by eric pouech (＠epo) 18 Feb '25

18 Feb '25

This merge request was approved by eric pouech. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7322

1 0

[PATCH v3 0/2] MR7345: server: Add order for registry value.
by Haoyang Chen (＠chenhaoyang) 18 Feb '25

18 Feb '25

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=9314 -- v3: server: Store the order for registry value. https://gitlab.winehq.org/wine/wine/-/merge_requests/7345

2 2

[PATCH v2 0/2] MR7345: server: Add order for registry value.
by Haoyang Chen (＠chenhaoyang) 18 Feb '25

18 Feb '25

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=9314 -- v2: server: Store the order for registry value. https://gitlab.winehq.org/wine/wine/-/merge_requests/7345

2 2

[PATCH 0/1] MR7345: server: Add order for registry value.
by Haoyang Chen (＠chenhaoyang) 18 Feb '25

18 Feb '25

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=9314 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7345

3 3

[PATCH 0/1] MR7348: winecoreaudio: Avoid duplicate Program Change or Channel Aftertouch MIDI messages.
by Brendan Shanks (＠bshanks) 18 Feb '25

18 Feb '25

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=57805 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7348

3 2

Re: [PATCH v6 0/6] MR7174: rtworkq: Fix handling of platform startup and lock counts.
by Conor McCarthy (＠cmccarthy) 18 Feb '25

18 Feb '25

On Tue Feb 18 06:30:29 2025 +0000, Nikolay Sivov wrote: > I knew I commented on these changes before, but then I found it was > !7244. Could we merge those, or what's the plan? No problem to do that if 11 commits are ok. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7174#note_94962

1 0

[PATCH v5 0/6] MR7174: rtworkq: Fix handling of platform startup and lock counts.
by Conor McCarthy (＠cmccarthy) 18 Feb '25

18 Feb '25

Startup and lock counts in native Windows are separate, and the lock count does not decrease when an async result is freed if the platform has been started. -- v5: rtworkq: Introduce an async result object cache. rtworkq: Introduce a platform startup count. rtworkq/tests: Test work queue. mfplat/tests: Test platform startup and lock counts. mfplat/tests: Test mixing of MF platform functions with their Rtwq equivalents. https://gitlab.winehq.org/wine/wine/-/merge_requests/7174

2 6

2025

2024

2023

2022

wine-gitlab February 2025