January 2025 - wine-gitlab

[PATCH v2 0/4] MR7219: win32u, winex11.drv: Fix multiple Vulkan surfaces handling.
by Paul Gofman (＠gofman) 28 Jan '25

28 Jan '25

-- v2: winex11.drv: Attach currently active Vulkan onscreen surface in vulkan_surface_update_offscreen(). win32u: Don't invalidate existing Vulkan surface when a new one is created for window. win32u: Check for NULL hwnd before calling vulkan_surface_presented() driver callback. https://gitlab.winehq.org/wine/wine/-/merge_requests/7219

4 7

[PATCH 0/4] MR7219: win32u, winex11.drv: Fix multiple Vulkan surfaces handling.
by Paul Gofman (＠gofman) 28 Jan '25

28 Jan '25

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

4 11

Re: [PATCH v6 0/0] MR7131: DIR command improvements: Make /o by itself behave equal to how it does in Windows
by Joe Souza (＠JoeS209) 28 Jan '25

28 Jan '25

After spending some time looking at the existing code, I find that it's not that far off from working properly. It correctly allows for multiple options to be specified on the command line, and correctly handles the exclusive options (i.e. of /N, /E, /S, /T, it correctly allows only one of these to take effect). What it gets wrong is that in Windows, the first of the exclusive options encountered takes precedence, where in current Wine code, it's the last exclusive option encountered that takes precedence. Current wine code also does not sort directory names for /G. All that in mind, the code does not need to be changed to allow multiple sort options to be passed to the qsort algorithm. We could clean up the use of global variables a bit, and sort the directory names for /G. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7131#note_93086

1 0

[PATCH v3 0/1] MR7158: wine.inf.in: Add UBR key
by Etaash Mathamsetty (＠etaash.mathamsetty) 28 Jan '25

28 Jan '25

Required by Logitech G Hub -- v3: wine.inf.in: Add UBR key. https://gitlab.winehq.org/wine/wine/-/merge_requests/7158

4 3

[PATCH 0/3] MR7182: winex11: Keep track and use expected window focus time on WM_STATE changes.
by Rémi Bernon (＠rbernon) 28 Jan '25

28 Jan '25

This is an attempt at improving X11 focus handling, and will most importantly be useful to later better handle dynamic window decoration changes on any mutter-based window manager. These window managers do a little dance in that case, unmapping/mapping the window every time decoration are added/removed, and we often get confused by the focus events it triggers. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7182

3 4

Re: [PATCH v2 0/3] MR7213: mountmgr: Set more registry values for serial and parport devices.
by Hans Leidekker (＠hans) 28 Jan '25

28 Jan '25

Right, GPUs and monitors. I don't think it's that much of a hack considering that we're already setting registry values here but I'll look into a PnP function driver. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7213#note_93083

1 0

Re: [PATCH v2 0/3] MR7213: mountmgr: Set more registry values for serial and parport devices.
by Elizabeth Figura (＠zfigura) 28 Jan '25

28 Jan '25

> We don't do that for all devices and it's not clear to me what we would gain by doing so. Well, it'd be significantly more correct. That often counts for a lot. As far as I can think of, the only devices for which we don't use the PnP architecture, and instead perform this kind of hack, are the GPU devices. That's because they're kind of tied to the explorer process rather than being able to be enumerated from winedevice. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7213#note_93082

1 0

Re: [PATCH v2 0/3] MR7213: mountmgr: Set more registry values for serial and parport devices.
by Hans Leidekker (＠hans) 28 Jan '25

28 Jan '25

We don't do that for all devices and it's not clear to me what we would gain by doing so. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7213#note_93076

1 0

Re: [PATCH v2 0/3] MR7213: mountmgr: Set more registry values for serial and parport devices.
by Elizabeth Figura (＠zfigura) 28 Jan '25

28 Jan '25

Should we implement this the proper way, with an actual PNP function driver? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7213#note_93074

1 0

[PATCH 0/2] MR7217: dinput: Clamp FFB effect report value to the field range.
by Rémi Bernon (＠rbernon) 28 Jan '25

28 Jan '25

Superseding https://gitlab.winehq.org/wine/wine/-/merge_requests/7161 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7217

3 4

2025

2024

2023

2022

wine-gitlab January 2025