December 2025 - Wine-gitlab

[PATCH v2 0/3] MR9646: mf/tests: Scrubbing tests
by Brendan McGrath (＠redmcg) 08 Dec '25

08 Dec '25

This MR adds tests for how scrubbing and rate changes work within the Media Session. -- v2: mf/tests: Check that Rate change in PLAY state is ignored. mf/tests: Test that there is no pre-roll during scrubbing. mf/tests: Modify test_seek_clock_sink to be ref counted. https://gitlab.winehq.org/wine/wine/-/merge_requests/9646

2 6

[PATCH 0/6] MR9718: amstream, quartz, ir50_32: Plumb the sample rect.
by Elizabeth Figura (＠zfigura) 07 Dec '25

07 Dec '25

Earth 2150 uses this. This fixes a regression from 2f180106471a41fa3d95f21919b87b94d8e13e63. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9718

2 6

[PATCH v2 0/3] MR9717: winegstreamer: Handle dynamic format change.
by Elizabeth Figura (＠zfigura) 07 Dec '25

07 Dec '25

-- v2: winegstreamer: Handle dynamic format change. https://gitlab.winehq.org/wine/wine/-/merge_requests/9717

2 4

[PATCH 0/3] MR9717: winegstreamer: Handle dynamic format change.
by Elizabeth Figura (＠zfigura) 07 Dec '25

07 Dec '25

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

2 3

[PATCH v8 0/11] MR9628: user32: Implement pointer input APIs for multi-touch support
by Hecheng Yu (＠kde-yyds) 07 Dec '25

07 Dec '25

This patch implements core pointer input APIs required by modern applications with touchscreen support, particularly Chromium and Qt-based applications. Implemented APIs: - GetPointerType: Query pointer input type (touch, pen, mouse) - GetPointerTouchInfo: Retrieve detailed touch pointer information - GetPointerFrameTouchInfo: Get all active touch pointers in current frame Added stubs: - SkipPointerFrameMessages: Used by applications to skip pointer frame processing like Qt - GetPointerFrameTouchInfoHistory: Historical touch frame data (not yet implemented) - GetPointerPenInfoHistory: Historical pen data (not yet implemented) System metrics changes: - SM_DIGITIZER: Reports touch capabilities (NID_INTEGRATED_TOUCH | NID_MULTI_INPUT | NID_READY) - SM_MAXIMUMTOUCHES: Returns maximum simultaneous touch points (10) Limitations: - We explictly set pointer type to PT_TOUCH when storing pointer info to queue, so GetPointerType will always return PT_TOUCH - GetPointerFrameTouchInfo returns 0 pointers after finger lift, while Windows returns 1 pointer with UP flags. And SkipPointerFrameMessages is currently a stub returning TRUE. Qt's pointer message processing uses both of them, but it's just working well Application requirements: - Chromium: Requires GetPointerType and GetPointerTouchInfo for touch input - Qt applications: Need GetPointerFrameTouchInfo and proper system metrics for multi-touch support - Qt5: Additionally checks for presence of all pointer APIs at runtime, requiring stubs to enable pointer messages processing -- v8: user32: Implement GetPointerFrameTouchInfo win32u: Implement NtUserGetPointerFrameTouchInfo user32: Implement GetPointerTouchInfo win32u: Implement NtUserGetPointerTouchInfo user32: Implement GetPointerType win32u: Implement NtUserGetPointerType win32u: Add pointer information cache and storage user32: Stub GetPointerPenInfoHistory user32: Stub GetPointerFrameTouchInfoHistory user32: Stub SkipPointerFrameMessages win32u: Add SM_DIGITIZER and SM_MAXIMUMTOUCHES system metrics https://gitlab.winehq.org/wine/wine/-/merge_requests/9628

2 11

[PATCH v3 0/5] MR9651: dmsynth: More robust sink write and render scheduling
by Anton Baskanov (＠baskanov) 07 Dec '25

07 Dec '25

-- v3: dmsynth: Clear the buffer notifications before closing the event handle. dmsynth: Estimate a continuously-advancing buffer position for a more precise timing. dmsynth: Call GetCurrentPosition from a separate thread. dmsynth: Simplify synth_sink_wait_play_end by making it similar to the main rendering loop. dmsynth: Try to maintain a fixed write latency by varying the wait time. https://gitlab.winehq.org/wine/wine/-/merge_requests/9651

2 6

[PATCH v16 0/7] MR9371: kernel32: Implement TH32CS_SNAPMODULE32 support for CreateToolhelp32Snapshot.
by Yuxuan Shui (＠yshui) 06 Dec '25

06 Dec '25

Intention is to use `CreateToolhelp32Snapshot` in `dbghelp.dll: EnumerateLoadedModulesW64`. Right now we can't because `CreateToolhelp32Snapshot` can't capture 32bit modules in wow64 processes, which is needed to support `SYMOPT_INCLUDE_32BIT_MODULES`. The advantage of using `CreateToolhelp32Snapshot` in mainly performance. Right now `EnumerateLoadedModulesW64` is `O(n^2)`, because of each module it calls `GetModuleInformation` which is itself `O(n)` w.r.t. number of modules. Whereas with `CreateToolhelp32Snapshot` there is no need for `GetModuleInformation`, thus reduce the complexity to just `O(n)`. * * * P.S. I am also uncomfortable with the amount of similar code between `CreateToolhelp32Snapshot` and `EnumProcessModulesEx`. Can something be done here? -- v16: kernel32: Implement TH32CS_SNAPMODULE32 support for CreateToolhelp32Snapshot. kernel32: Use GetCurrentProcess() handle in CreateToolhelp32Snapshot if possible. kernel32/tests: Test CreateToolhelp32Snapshot with TH32CS_SNAPMODULE32. kernel32: Fix CreateToolhelp32Snapshot on old WoW64. include: Add TH32CS_SNAPMODULE32. kernel32/tests: Handle ERROR_BAD_LENGTH from CreateToolhelp32Snapshot. kernel32/tests: Fix CreateToolhelp32Snapshot failure check. https://gitlab.winehq.org/wine/wine/-/merge_requests/9371

2 7

[PATCH v7 0/11] MR9628: user32: Implement pointer input APIs for multi-touch support
by Hecheng Yu (＠kde-yyds) 06 Dec '25

06 Dec '25

This patch implements core pointer input APIs required by modern applications with touchscreen support, particularly Chromium and Qt-based applications. Implemented APIs: - GetPointerType: Query pointer input type (touch, pen, mouse) - GetPointerTouchInfo: Retrieve detailed touch pointer information - GetPointerFrameTouchInfo: Get all active touch pointers in current frame Added stubs: - SkipPointerFrameMessages: Used by applications to skip pointer frame processing like Qt - GetPointerFrameTouchInfoHistory: Historical touch frame data (not yet implemented) - GetPointerPenInfoHistory: Historical pen data (not yet implemented) System metrics changes: - SM_DIGITIZER: Reports touch capabilities (NID_INTEGRATED_TOUCH | NID_MULTI_INPUT | NID_READY) - SM_MAXIMUMTOUCHES: Returns maximum simultaneous touch points (10) Limitations: - We explictly set pointer type to PT_TOUCH when storing pointer info to queue, so GetPointerType will always return PT_TOUCH - GetPointerFrameTouchInfo returns 0 pointers after finger lift, while Windows returns 1 pointer with UP flags. And SkipPointerFrameMessages is currently a stub returning TRUE. Qt's pointer message processing uses both of them, but it's just working well Application requirements: - Chromium: Requires GetPointerType and GetPointerTouchInfo for touch input - Qt applications: Need GetPointerFrameTouchInfo and proper system metrics for multi-touch support - Qt5: Additionally checks for presence of all pointer APIs at runtime, requiring stubs to enable pointer messages processing -- v7: user32: Implement GetPointerFrameTouchInfo win32u: Implement NtUserGetPointerFrameTouchInfo user32: Implement GetPointerTouchInfo win32u: Implement NtUserGetPointerTouchInfo user32: Implement GetPointerType win32u: Implement NtUserGetPointerType win32u: Add pointer information cache and storage user32: Stub GetPointerPenInfoHistory user32: Stub GetPointerFrameTouchInfoHistory user32: Stub SkipPointerFrameMessages win32u: Add SM_DIGITIZER and SM_MAXIMUMTOUCHES system metrics https://gitlab.winehq.org/wine/wine/-/merge_requests/9628

2 11

Re: [PATCH v6 0/11] MR9628: user32: Implement pointer input APIs for multi-touch support
by Hecheng Yu (＠kde-yyds) 06 Dec '25

06 Dec '25

On Mon Dec 1 14:57:26 2025 +0000, Hecheng Yu wrote: > For new APIs maybe yes Now splited. Tests will also appear later. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9628#note_125084

1 0

Re: [PATCH v2 0/3] MR9640: oleaut32: Fix MSVC generating _VtblGapPlaceholder methods for typelib headers
by Mircea Roată-Palade 06 Dec '25

06 Dec '25

Should the case when both `LOAD_TLB_AS_32BIT` and `LOAD_TLB_AS_64BIT` are passed be handled/tested? It's extremely unlikely both flags are passed together by any sane program, however I expected this case to be an error, but it turns out the flags are just ignored and the typelib is loaded with the native pointer size. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9640#note_125080

1 0