February 2024 - Wine-GitLab

[PATCH v2 0/1] MR3783: user32/tests: Register test_hvredraw class in temp desktop.
by Esme Povirk (＠madewokherd) March 15, 2025

March 15, 2025

Windows v1709 has a bug that breaks GetClassLong on a different desktop from where the class was registered. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55539 -- v2: user32/tests: Register test_hvredraw class in temp desktop. https://gitlab.winehq.org/wine/wine/-/merge_requests/3783

3 3

[PATCH 0/2] MR3788: iphlpapi/tests: Call GetAdaptersAddresses() in a loop.
by Hans Leidekker (＠hans) March 15, 2025

March 15, 2025

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

4 4

[PATCH 0/1] MR3783: user32/tests: Register test_hvredraw class in temp desktop.
by Esme Povirk (＠madewokherd) March 10, 2025

March 10, 2025

Windows v1709 has a bug that breaks GetClassLong on a different desktop from where the class was registered. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55539 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3783

4 5

[PATCH v2 0/1] MR3774: gdiplus/tests: Extend DrawImage scaling tests.
by Bartosz Kosiorek (＠gang65) March 10, 2025

March 10, 2025

Changing the colour of the second pixel of the source bitmap clarifies the incorrect behaviour of PixelOffsetMode Half and HighQuality. This also provides better proof that PixelOffsetMode None and Fast are implemented correctly. Extending tests is starting point for further improvements of implementation pixel offset modes to match implementation from native gdiplus. -- v2: gdiplus/tests: Extend DrawImage scaling tests. https://gitlab.winehq.org/wine/wine/-/merge_requests/3774

4 4

[PATCH 0/2] MR3735: user32/tests: Wait for GetMessage call to complete.
by Esme Povirk (＠madewokherd) March 9, 2025

March 9, 2025

It's possible otherwise for the second message to be sent before GetMessage removes a posted message from the queue, in which case GetMessage processes both sent messages. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54407 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/3735

3 3

[PATCH 0/1] MR3720: wtsapi/tests: Use a heap buffer for the user SID.
by Hans Leidekker (＠hans) March 9, 2025

March 9, 2025

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

3 2

[PATCH 0/1] MR3721: webservices/tests: Fully initialize xmlstr.
by Hans Leidekker (＠hans) March 9, 2025

March 9, 2025

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

3 2

[PATCH 0/1] MR3719: d3d9/tests: Don't fail d3d9ex if the window manager restores focus too soon.
by Stefan Dösinger March 9, 2025

March 9, 2025

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

4 5

[PATCH v4 0/4] MR3675: dmsynth/tests: Test the synthesizer components and render some samples from MIDI.
by Rémi Bernon March 8, 2025

March 8, 2025

-- v4: dmsynth/tests: Test DirectMusicSynth class in isolation. dmsynth/tests: Test DirectMusicSynthSink class in isolation. dmsynth/tests: Import and use a check_interface helper. dmsynth/tests: Avoid dynamic format string. https://gitlab.winehq.org/wine/wine/-/merge_requests/3675

3 10

[PATCH 0/9] MR5057: Draft: winewayland.drv: Use virtual display devices to implement mode change emulation
by Alexandros Frantzis (＠afrantzis) March 7, 2025

March 7, 2025

This WIP branch prototypes the usage of virtual display devices (through "virtual desktop" mode at the moment) to support display mode emulation in the Wayland driver. It works by allowing the driver to mark each host adapter with a virtual_id, which, if present, signals to win32u that it should include the adapter in the virtual display configuration. The virtual configuration (along with the virtual ids) is reported back to the driver though a new user driver function. If none of the host adapters is marked with a virtual id (i.e., all other drivers) we fall back to the single virtual display mode as before. Some deficiencies and open questions with the prototype: 1. Virtual desktop mode implies a lot of behavior that we don't want at this point the Wayland driver (e.g., taskbar window, changing the display mode to the virtual desktop resolution at startup, some changes in fsclip behavior). One way forward would be to have a "virtual display devices" mode separate from the "virtual desktop" mode, so that drivers can opt in only to the desired behavior (virtual desktop would imply virtual devices, to maintain the current behavior). 2. It's not clear to me what would be the best way for a driver to opt in or out of certain core behavior. Perhaps the driver would change some volatile registry key which other components would consult? Or introduce a user driver function for core to query the driver about such features on demand? Is there some precedence I can get inspiration from? 3. At the moment, the prototype calls the new "NotifyVirtualDevices" user driver callback only in the process which the display update occurred. This means that other processes don't get notified of the virtual devices mapping to host devices, so, in the Wayland driver case, we are not able to scale windows from those processes properly. One approach would be for core to ensure that the NotifyVirtualDevices callback is called once in all processes, but I am not sure what's the best way to achieve this (or even if this is the preferred approach). Another way would be to have a mechanism for the driver to query the virtual device info (+mappings) on demand, and just broadcast a message to all windows. In this case it could even be done internally by the driver (so more in line with what the part-12 MR is doing), if we don't want to introduce a more global behavior. Perhaps there is some even better mechanism, which would also be more fitting to how we envision the virtual display/devic es to evolve going forward. Let me know what you think! -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5057

5 25