- Wine-GitLab - list.winehq.org

Re: [PATCH v3 0/6] MR9468: mmdevapi: Various - approved
by Alexandre Julliard (＠julliard) Nov. 18, 2025

Nov. 18, 2025

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

1 0

[PATCH v2 0/4] MR9518: Draft: wined3d: Initial partial presentation implementation
by Andrew Boyarshin (＠andrew-boyarshin) Nov. 18, 2025

Nov. 18, 2025

Based on !9515 (this MR is a draft until the first part is accepted). This is most of the logic of partial presentation. D3D11 only. Remaining parts: 1. Support for multiple rectangles. Requires changes to command stream and swapchain present op (GL, VK, GDI). I have it implemented, but I'm not confident in my implementation, so it must be a separate review. 2. Scroll. Simple grep.app search shows very little use. Neither Firefox nor Chromium use that. Windows Terminal is the most prominent. So this is low priority (though I have it implemented, it's not very difficult). 3. D3D12. I know of no apps that do partial presentation with D3D12. Most of my experience is with D2D & DComp, I barely have experience with D3D11, D3D12 is even more complicated, so I do not plan on implementing it. 4. Other scaling modes (see TODO). I don't think Wine implements them for D3D11. 5. Performance improvement? Right now dirty backbuffer regions are always tracked for correctness. I bet Windows does it better in the most common cases when there is no partial presentation. -- v2: wined3d: Initial partial present implementation wined3d: Track the dirty regions of the swapchain backbuffers https://gitlab.winehq.org/wine/wine/-/merge_requests/9518

2 4

[PATCH 0/4] MR9518: Draft: wined3d: Initial partial presentation implementation
by Andrew Boyarshin (＠andrew-boyarshin) Nov. 18, 2025

Nov. 18, 2025

Based on !9515 (this MR is a draft until the first part is accepted). This is most of the logic of partial presentation. D3D11 only. Remaining parts: 1. Support for multiple rectangles. Requires changes to command stream and swapchain present op (GL, VK, GDI). I have it implemented, but I'm not confident in my implementation, so it must be a separate review. 2. Scroll. Simple grep.app search shows very little use. Neither Firefox nor Chromium use that. Windows Terminal is the most prominent. So this is low priority (though I have it implemented, it's not very difficult). 3. D3D12. I know of no apps that do partial presentation with D3D12. Most of my experience is with D2D & DComp, I barely have experience with D3D11, D3D12 is even more complicated, so I do not plan on implementing it. 4. Other scaling modes (see TODO). I don't think Wine implements them for D3D11. 5. Performance improvement? Right now dirty backbuffer regions are always tracked for correctness. I bet Windows does it better in the most common cases when there is no partial presentation. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9518

2 4

[PATCH v9 0/1] MR5373: shell32: Implement FCIDM_SHVIEW_CREATELINK
by Aric Stewart (＠aricstewart) Nov. 18, 2025

Nov. 18, 2025

Presently the wine file explorer has a create shortcut entry that does nothing. This implements the FCIDM_SHVIEW_CREATELINK command. This is a patch that was first submitted in 2017 and I unfortunately let the revision request fall unimplemented. -- v9: shell32: Implement FCIDM_SHVIEW_CREATELINK https://gitlab.winehq.org/wine/wine/-/merge_requests/5373

3 6

[PATCH v3 0/2] MR9501: msxml3: Add normalize-line-breaks sax feature.
by Vijay Kiran Kamuju (＠infyquest) Nov. 18, 2025

Nov. 18, 2025

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=36686 -- v3: msxml3: Add normalize-line-breaks sax feature. msxml3/tests: Fix schema-validation sax feature tests. https://gitlab.winehq.org/wine/wine/-/merge_requests/9501

3 4

[PATCH v3 0/5] MR9506: dmsynth: DLS fixes, part 1
by Anton Baskanov (＠baskanov) Nov. 18, 2025

Nov. 18, 2025

-- v3: dmsynth: Use a factor of 1/10 for modulation LFO x channel pressure -> gain connections. dmsynth: Handle channel pressure events. dmsynth: Don't add 1000 to the sustain modulators. dmsynth: Use 0.1% as the sustain level unit. dmsynth/tests: Add DLS tests. https://gitlab.winehq.org/wine/wine/-/merge_requests/9506

4 10

[PATCH 0/6] MR9517: d3dx{9,10,11}: Implement a box filter.
by Connor McAdams (＠cmcadams) Nov. 18, 2025

Nov. 18, 2025

This MR also includes some test code cleanup based on comments [here.](https://gitlab.winehq.org/wine/wine/-/merge_requests/9206#note_12068… -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9517

2 6

[PATCH v2 0/6] MR9453: xactengine3/tests: Add many more tests.
by Elizabeth Figura (＠zfigura) Nov. 18, 2025

Nov. 18, 2025

-- v2: xactengine3/tests: Test wavebank type mismatch. xactengine3/tests: Test SetMatrixCoefficients() channel counts. xactengine3/tests: Test variables. xactengine3/tests: Test renderer details. https://gitlab.winehq.org/wine/wine/-/merge_requests/9453

2 6

[PATCH 0/1] MR9516: jscript: Do existing prop lookups for external props only on objects with volatile props.
by Gabriel Ivăncescu Nov. 18, 2025

Nov. 18, 2025

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

1 1

[PATCH v2 0/3] MR9511: Draft: server: Forbid background process window reactivation.
by Rémi Bernon Nov. 18, 2025

Nov. 18, 2025

Pegasus Mail posts a WM_USER + 8991 message to its own window when it loses focus, then calls SetFocus on its window when processing this message. Several other applications have been seen calling SetWindowPos during WM_ACTIVATE message, which might also attempt to reactivate the window. That processing happens shortly after we have changed the foreground window to the desktop window, when focus is lost, then SetFocus tries to change the foreground window again. This SetFocus behavior is tested, and should work like this, but would only activate the window if the process is allowed to do so. Windows has various rules around this, and it seems to boil down to something like: * Allow taking focus if the process never was foreground, ie: when process is starting and gets initial focus on its windows. * Allow taking focus if the process was foreground but lost it recently because of a window being destroyed. * Forbid taking focus back if the process had foreground and called SetForegroundWindow explicitly to give it to another process. This doesn't implement all this rules, but rather keep rely on the host window management with some additional heuristics to avoid activating windows which lost foreground recently. This is mostly about keeping track of user input time, updating it on user input and on focus change. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=58167 --- I think this should be enough to prevent spurious window reactivation, either from calls to SetWindowPos during WM_ACTIVATE messages like in https://gitlab.winehq.org/wine/wine/-/merge_requests/9398 or from calls to SetFocus from posted messages right after window deactivation as described above. Fwiw we could have tests for that, and show that this MR is fixing them but fvwm doesn't implement window minimization properly, and doesn't change focus when window is minimized, so the tests would be meaningless. -- v2: server: Forbid background process window reactivation. server: Set NULL foreground input when switching to desktop window. win32u: Introduce a NtUserSetForegroundWindowInternal call. https://gitlab.winehq.org/wine/wine/-/merge_requests/9511

1 4