June 2024 - Wine-GitLab - list.winehq.org

Re: [PATCH v5 0/6] MR5870: mmdevapi: Implement loopback capture with winepulse backend. - approved
by Alexandre Julliard (＠julliard) June 26, 2024

June 26, 2024

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

1 0

Re: [PATCH v2 0/1] MR5928: msado15: Support interface ADOCommandConstruction in _Command - approved
by Alexandre Julliard (＠julliard) June 26, 2024

June 26, 2024

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

1 0

Re: [PATCH v3 0/2] MR5927: quartz: Implement IVMRWindowlessControl::GetNativeVideoSize(). - approved
by Alexandre Julliard (＠julliard) June 26, 2024

June 26, 2024

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

1 0

[PATCH 0/1] MR5936: mscoree: Update Wine Mono to 9.2.0.
by Esme Povirk (＠madewokherd) June 26, 2024

June 26, 2024

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

3 2

Re: [PATCH v2 0/1] MR5909: comctl32/listview: Prevent LISTVIEW_GetNextItem failure after checking last item state in list
by Ilia Docin (＠IDocin) June 26, 2024

June 26, 2024

On Wed Jun 26 07:26:50 2024 +0000, Zhiyi Zhang wrote: > This looks correct at first glance. Do you have an application affected > by this? It seems to me changing this only reduces some time and -1 will > be returned if it's the last item. Yes, I have. It fails on asserting return value of sending LVM_GETNEXTITEM message. I agree about aftereffect of this fix. Anyway, for me it doesn't make sense to handle ahead of time incorrect item (== infoPtr->nItemCount). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5909#note_74482

1 0

Re: [PATCH v5 0/1] MR5706: comctl32/rebar: Hide chevron if rebar's band is resized back to full size with gripper
by Ilia Docin (＠IDocin) June 26, 2024

June 26, 2024

On Wed Jun 26 07:15:20 2024 +0000, Zhiyi Zhang wrote: > Do you have a link to the software you used to demonstrate? No. It's a commercial software. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5706#note_74478

1 0

[PATCH v2 0/6] MR5926: ntdll: Always fill the 32-bit IOSB when performing I/O on overlapped handles.
by Elizabeth Figura (＠zfigura) June 26, 2024

June 26, 2024

Previously it was assumed that synchronous I/O fills the 64-bit IOSB, and asynchronous I/O fills the 32-bit IOSB. As the ntdll:wow64 tests show, this is incorrect. I/O on an overlapped handle, whether it is synchronous or not, fills the 32-bit IOSB, and I/O on a non-overlapped handle always fills the 64-bit IOSB. The first half is important, since completion can be signaled before we even return from the initial I/O call [NtReadFile() etc.] Filling the IOSB after signaling completion is the cause of bug 56389. This patch series fixes that. The second discrepancy does not cause any bugs, as far as I can see, and is a bit harder to fix anyway. It is therefore not addressed by this patch series. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56389 -- v2: ntdll: Always fill the 32-bit iosb for overlapped handles, for regular read/write. ntdll: Always fill the 32-bit iosb for overlapped handles, in set_async_direct_result(). ntdll: Always fill the 32-bit iosb for overlapped handles, in file_complete_async(). https://gitlab.winehq.org/wine/wine/-/merge_requests/5926

2 7

[PATCH 0/10] MR5934: ntdll: Improvements related to preferred UI languages
by Piotr Caban (＠piotr) June 26, 2024

June 26, 2024

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

2 10

[PATCH v4 0/6] MR5870: mmdevapi: Implement loopback capture with winepulse backend.
by Paul Gofman (＠gofman) June 26, 2024

June 26, 2024

-- v4: mmdevapi/tests: Add test for capturing render loopback. winepulse.drv: Implement pulse_get_loopback_capture_device(). winepulse.drv: Factor out wait_pa_operation_complete(). mmdevapi: Stub AUDCLNT_STREAMFLAGS_LOOPBACK support. mmdevapi: Adjust timing after main loop start in client_Initialize(). https://gitlab.winehq.org/wine/wine/-/merge_requests/5870

4 9

[PATCH 0/6] MR5926: ntdll: Always fill the 32-bit IOSB when performing I/O on overlapped handles.
by Elizabeth Figura (＠zfigura) June 26, 2024

June 26, 2024

Previously it was assumed that synchronous I/O fills the 64-bit IOSB, and asynchronous I/O fills the 32-bit IOSB. As the ntdll:wow64 tests show, this is incorrect. I/O on an overlapped handle, whether it is synchronous or not, fills the 32-bit IOSB, and I/O on a non-overlapped handle always fills the 64-bit IOSB. The first half is important, since completion can be signaled before we even return from the initial I/O call [NtReadFile() etc.] Filling the IOSB after signaling completion is the cause of bug 56389. This patch series fixes that. The second discrepancy does not cause any bugs, as far as I can see, and is a bit harder to fix anyway. It is therefore not addressed by this patch series. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56389 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5926

3 7