- wine-gitlab - winehq.org

[PATCH v2 0/1] MR7221: ieframe: Add IShellWindows stub implementation.
by Helix Graziani (＠TornadoCookie) 29 Jan '25

29 Jan '25

-- v2: ieframe: Add IShellWindows stub implementation. https://gitlab.winehq.org/wine/wine/-/merge_requests/7221

3 3

[PATCH 0/1] MR7221: ieframe: Add IShellWindows stub implementation.
by Helix Graziani (＠TornadoCookie) 29 Jan '25

29 Jan '25

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

3 2

Re: [PATCH v3 0/7] MR3909: winewayland.drv: part 7: Basic window management
by Dominic Hayes - Feren OS Dev (＠dominichayesferen) 29 Jan '25

29 Jan '25

I know it's been a year, but I'm not sure where else would be best to ask this, so: Are there plans to support XDG_DECORATION in WINE ~11, and will it prefer SSDs on the application-side? Aside from that, for those who have to deal with the CSD titlebars, is there any desire to upgrade the CSDs from Windows Classic to Windows Basic CSDs? All the textures for Windows Basic exist in Windows XP msstyles, afterall, given Windows Basic derivatives from Windows XP's window manager afterall, and this solution would also ensure consistency with programs that use Windows Basic's textures such as Mozilla Firefox. Upgrading the CSDs to Windows Basic, especially now they're exposed to users as a requirement in GNOME, would likely be the preferred way, for users of visual styles, to have the CSDs be improved, would still provide the opportunity for WINE to have its own custom window decorations due to the WINE Visual Style, and would also preserve the Windows Classic CSDs for users who opt out of Visual Styles entirely. If GNOME CSDs are desired later down the line, those could be supplied via the "Use GTK+ theme as Visual Style" experiment or new Wine Configuration option. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3909#note_93141

1 0

[PATCH v2 0/1] MR7172: win32u: Implement a couple of syscalls.
by Paul Gofman (＠gofman) 28 Jan '25

28 Jan '25

-- v2: win32u: Implement NtUserGetCurrentInputMessageSource(). https://gitlab.winehq.org/wine/wine/-/merge_requests/7172

3 2

Re: [PATCH v3 0/4] MR7219: win32u, winex11.drv: Fix multiple Vulkan surfaces handling. - approved
by Alexandre Julliard (＠julliard) 28 Jan '25

28 Jan '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7219

1 0

Re: [PATCH v3 0/1] MR7121: winex11: Allow Withdrawn requests to override Iconic <-> Normal transitions. - approved
by Alexandre Julliard (＠julliard) 28 Jan '25

28 Jan '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7121

1 0

Re: [PATCH v2 0/1] MR7043: include: Add signbit declarations for c++. - approved
by Alexandre Julliard (＠julliard) 28 Jan '25

28 Jan '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7043

1 0

Re: [PATCH v2 0/2] MR7217: dinput: Clamp FFB effect report value to the field range. - approved
by Alexandre Julliard (＠julliard) 28 Jan '25

28 Jan '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7217

1 0

Re: [PATCH v2 0/1] MR7209: hhctrl: Use wide character string literals. - approved
by Alexandre Julliard (＠julliard) 28 Jan '25

28 Jan '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7209

1 0

Re: [PATCH v2 0/1] MR7208: cryptui: Use wide character string literals. - approved
by Alexandre Julliard (＠julliard) 28 Jan '25

28 Jan '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7208

1 0

Re: [PATCH v13 0/2] MR7169: ntdll: Fix the return value of NtDelayExecution. - approved
by Alexandre Julliard (＠julliard) 28 Jan '25

28 Jan '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7169

1 0

[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

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

[PATCH v3 0/4] MR7216: winebth.sys part 3: Introduce IOCTLs related to radio discoverability, connectability and device inquiry.
by Vibhav Pant (＠vibhavp) 28 Jan '25

28 Jan '25

The Windows Bluetooth stack uses private IOCTLs in order to set the [discoverability](https://learn.microsoft.com/en-us/windows/win32/api/blueto… and [connectability](https://learn.microsoft.com/en-us/windows/win32/api/bluetoo… status of a local radio, and to start/stop the device inquiry procedure. This MR introduces 3 wine-specific IOCTL codes for the same purposes, as most applications seem to the Win32 API itself for these operations: * IOCTL_WINBTH_RADIO_SET_FLAG * IOCTL_WINEBTH_RADIO_START_DISCOVERY * IOCTL_WINEBTH_RADIO_STOP_DISCOVERY -- v3: winebth.sys: Call bluez_watcher_close as part of bluetooth_shutdown. winebth.sys: Implement IOCTL_WINEBTH_RADIO_STOP_DISCOVERY. winebth.sys: Implement IOCTL_WINEBTH_RADIO_START_DISCOVERY. https://gitlab.winehq.org/wine/wine/-/merge_requests/7216

2 4

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

28 Jan '25

Thank you! I opened !7217 with a couple of minor tweaks. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7161#note_93069

1 0

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

28 Jan '25

This merge request was closed by Rémi Bernon. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7161

1 0

[PATCH 0/4] MR7216: winebth.sys part 3: Introduce IOCTLs related to radio discoverability, connectability and device inquiry.
by Vibhav Pant (＠vibhavp) 28 Jan '25

28 Jan '25

The Windows Bluetooth stack uses private IOCTLs in order to set the [discoverability](https://learn.microsoft.com/en-us/windows/win32/api/blueto… and [connectability](https://learn.microsoft.com/en-us/windows/win32/api/bluetoo… status of a local radio, and to start/stop the device inquiry procedure. This MR introduces 3 wine-specific IOCTL codes for the same purposes, as most applications seem to the Win32 API itself for these operations: * IOCTL_WINBTH_RADIO_SET_FLAG * IOCTL_WINEBTH_RADIO_START_DISCOVERY * IOCTL_WINEBTH_RADIO_STOP_DISCOVERY -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7216

2 4

Re: [PATCH v5 0/5] MR7109: Added missing functions _FCbuild, cimag, crealf and cimagf
by Stéphane Bacri (＠fr33z00) 28 Jan '25

28 Jan '25

@piotr I shall admit I'm a bit confused by the fork way of working and the wine CI. I previously made some rebase, but now, when I click on the rebase button, nothing happens. I didn't want to bother you before the windows build pipelines were successful, but your offer is welcomed. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7109#note_93055

1 0

2025

2024

2023

2022

wine-gitlab