March 2025 - wine-gitlab

Re: [PATCH v2 0/1] MR7532: winedump: fix grep warning - approved
by Alexandre Julliard (＠julliard) 10 Mar '25

10 Mar '25

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

1 0

[PATCH v2 0/1] MR3774: gdiplus/tests: Extend DrawImage scaling tests.
by Bartosz Kosiorek (＠gang65) 10 Mar '25

10 Mar '25

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/1] MR7495: Draft: mfplat: Add mp3 resolver hint.
by Brendan McGrath (＠redmcg) 10 Mar '25

10 Mar '25

This MR is marked as draft as it is dependent on MR !7493. It adds two new resolver hints for the mp3 format: 1. The [MP3 frame header][1]; and 2. The [ID3v2.3 tag][2] I have two issues: 1. The MP3 frame header only has 14 bits enabled in the mask; and 2. ID3v2.3 tags aren't exclusive to mp3 Hence I'm raising this now for early feedback/ideas. As the game I'm looking to fix (ProgressBar95) includes MP3s with both these headers, but it uses a custom [IMFByteStream implementation][3] that … [View More]

3 6

[PATCH v3 0/7] MR7536: d3dx9, d3dcompiler test fixes, improvements
by Matteo Bruni (＠Mystral) 10 Mar '25

10 Mar '25

Thanks to Rémi Bernon for mentioning in !5814 the new test failure, which spurred the first patch of this MR. Then one thing led to another and somehow this whole MR happened... -- v3: d3dcompiler/tests: Add d3dcompiler_42 tests. d3dcompiler: Fix a few version-dependent error returns in D3DReflect(). d3dx9/tests: Add d3dx9_42 tests. d3dx9_42: Generate an import library. https://gitlab.winehq.org/wine/wine/-/merge_requests/7536

2 8

[PATCH 0/1] MR7517: ntdll: Do not fail NtCreateUserProcess() if requested access doesn't have PROCESS_CREATE_THREAD.
by Paul Gofman (＠gofman) 10 Mar '25

10 Mar '25

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

3 4

[PATCH v2 0/6] MR7536: d3dx9, d3dcompiler test fixes, improvements
by Matteo Bruni (＠Mystral) 10 Mar '25

10 Mar '25

Thanks to Rémi Bernon for mentioning in !5814 the new test failure, which spurred the first patch of this MR. Then one thing led to another and somehow this whole MR happened... -- v2: d3dcompiler/tests: Add d3dcompiler_42 tests. https://gitlab.winehq.org/wine/wine/-/merge_requests/7536

2 6

[PATCH 0/6] MR7536: d3dx9, d3dcompiler test fixes, improvements
by Matteo Bruni (＠Mystral) 10 Mar '25

10 Mar '25

Thanks to Rémi Bernon for mentioning in !5814 the new test failure, which spurred the the first patch of this MR. Then one thing led to another and somehow the whole MR happened... -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7536

2 6

[PATCH 0/2] MR7491: cmd: Introduce MODE command
by Alfred Agrell (＠Alcaro) 10 Mar '25

10 Mar '25

Like BUG-57912 and BUG-57913, this was encountered in https://www.smwcentral.net/?p=section&a=details&id=33546 (.resources/Lunar Magic/scripts/insert_all_patches.bat). Unfortunately, I was unable to write a passing test; winetest redirects the child's stdout to a file, so GetConsoleScreenBufferInfo fails. And some of those numbers will vary between machines. Should I just drop the test? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7491

3 4

[PATCH 0/1] MR7535: prntvpt: PageImageableSize capabilities depend on page orientation.
by Dmitry Timoshkov (＠dmitry) 10 Mar '25

10 Mar '25

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

2 1

[PATCH v2 0/2] MR7457: winewayland: Ignore enter motion during pointer lock.
by Attila Fidan (＠atticf) 10 Mar '25

10 Mar '25

Having a pointer lock implies that relative motion is also used. When refocusing on a mouselook application which the driver is using relative motion for, an absolute motion hardware input is sent because of handling the wl_pointer.enter event. This can result in an unwanted warp/jerk. The need to handle enter motion isn't applicable to mouselook or cases where the pointer is locked because the application is drawing its own cursor while covering vscreen, so it can be ignored during pointer … [View More]

3 4

2025

2024

2023

2022

wine-gitlab March 2025