- wine-gitlab - winehq.org

[PATCH 0/7] MR5150: Fix handling of DPI_AWARENESS_CONTEXT_PER_MONITOR_AWARE_V2
by Fabian Maurer (＠DarkShadow44) 26 Feb '24

26 Feb '24

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

3 8

[PATCH 0/1] MR5152: Draft: gdiplus: Avoid using GdipGetRegionHrgn in GdipFillPath
by David Kahurani (＠kahurani) 26 Feb '24

26 Feb '24

This is a half-witted attempt at avoiding GdipGetRegionHrgn. in GdipFillPath. The use of GdipGetRegionHrgn happens as consequence of the use of regions in internal code. From the look of it, as per the development plans, it should be possible to remove it by avoiding internal use of regions. This could be done, for instance, by reducing a region to a path before computing on it or rendering it. However, this is going to be fairly if not very complicated and, just like with the other MR, will not guarantee optimization. This patch, for instance, might not have observable optimization impact. This is because 'trace_path' and 'PathToRegion' are still being used and are probably the most computation heavy sections of GdipGetRegionHrgn. Still, it should be possible to compute the exactly what data to render without these two methods. This could however get a bit complicated. Signed-off-by: David Kahurani <k.kahurani(a)gmail.com> -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5152

4 11

[PATCH 0/5] MR5163: Explicitly request debug info in critical sections.
by Paul Gofman (＠gofman) 26 Feb '24

26 Feb '24

See https://gitlab.winehq.org/wine/wine/-/merge_requests/5071 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5163

4 7

[PATCH v3 0/3] MR5141: dmime: bandtrack for MIDI files
by Yuxuan Shui (＠yshui) 26 Feb '24

26 Feb '24

Create a bandtrack for MIDI files by picking out the MIDI 0xCn events, and creating matching DMUS_PATCH_PMSG. * * * This also has a commit adding a stub chordtrack, which is small so I think a separate MR is unwarranted. Can be split out if necessary. -- v3: dmime: Add a stub chordtrack for MIDI segments. https://gitlab.winehq.org/wine/wine/-/merge_requests/5141

5 12

[PATCH 0/1] MR674: tests: Test how constant folding works on SM1.
by Giovanni Mascellani (＠giomasce) 26 Feb '24

26 Feb '24

While reviewing !671 I wrote a few tests that are probably not too fundamental, but since now they exist it makes sense to keep them. !671 doesn't fix nor break any of them, anyway. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/674

5 16

[PATCH 0/1] MR678: vkd3d: Store a D3D12_RESOURCE_DESC structure in struct vkd3d_image_resource_create_info.
by Henri Verbeet (＠hverbeet) 26 Feb '24

26 Feb '24

-- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/678

2 1

[PATCH 0/1] MR5160: wbemprox: Handle implicit property in object path.
by Hans Leidekker (＠hans) 26 Feb '24

26 Feb '24

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

3 5

[PATCH 0/2] MR5166: netprofm: Support NLM_ENUM_NETWORK flags.
by Hans Leidekker (＠hans) 26 Feb '24

26 Feb '24

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

3 3

[PATCH 0/4] MR5161: Draft: d3drm: Implement Update and related functions
by Jeffrey Smith (＠whydoubt) 26 Feb '24

26 Feb '24

Regarding dirty rectangles:<br> Documentation for `ForceUpdate` states that "The system might update any region that is larger than the specified rectangle, including possibly the entire window". While native seems to use a sort of dirty-rectangle approach, for this MR, I am simply dirtying the entire surface. If someday someone did want to more-closely match the behavior of native, much can be learned from the rectangles passed to the update callbacks. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5161

2 5

[PATCH v2 0/7] MR5128: winevulkan: Use VK_EXT_map_memory_placed for memory mapping on wow64.
by Jacek Caban (＠jacek) 26 Feb '24

26 Feb '24

With the new extension, we may implement wow64 correctly, without `VK_EXT_external_memory_host` hacks. This is both more correct and more performant (essentially eliminating Vulkan wow64 performance penalty). -- v2: winevulkan: Use VK_EXT_map_memory_placed for memory mapping on wow64. winevulkan: Add support for VK_EXT_map_memory_placed. winevulkan: Refactor extra extensions handling in wine_vk_device_convert_create_info. winevulkan: Use handle map for memory objects. winevulkan: Rename wine_device_memory mapping to vm_map. https://gitlab.winehq.org/wine/wine/-/merge_requests/5128

4 15

2025

2024

2023

2022

wine-gitlab