February 2024 - Wine-GitLab

Re: [PATCH v2 0/2] MR5147: iphlpapi: Partially implement filling metrics in GetAdaptersAddresses(). - approved
by Alexandre Julliard (＠julliard) Feb. 26, 2024

Feb. 26, 2024

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

1 0

Re: [PATCH v2 0/1] MR5162: server: Allow 0-write length in WriteProcessMemory(). - approved
by Alexandre Julliard (＠julliard) Feb. 26, 2024

Feb. 26, 2024

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

1 0

Re: [PATCH v2 0/1] MR5154: shell32: Also zero-initialize the background menu. - approved
by Alexandre Julliard (＠julliard) Feb. 26, 2024

Feb. 26, 2024

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

1 0

Re: [PATCH v2 0/3] MR5144: gdiplus: Restore hdc argument to gdip_format_string. - approved
by Alexandre Julliard (＠julliard) Feb. 26, 2024

Feb. 26, 2024

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

1 0

Re: [PATCH v2 0/1] MR5149: oleaut32: Use scientific notation if it prevents a loss of accuracy. - approved
by Alexandre Julliard (＠julliard) Feb. 26, 2024

Feb. 26, 2024

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

1 0

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

Feb. 26, 2024

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. -- v2: tests: Test how constant folding works on SM1. https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/674

2 1

[PATCH 0/1] MR5168: configure: Disable -Wmisleading-indentation warnings on GCC.
by Jacek Caban (＠jacek) Feb. 26, 2024

Feb. 26, 2024

As discussed in !5148, it fixes GCC spamming build output to inform users that about its non-flexible memory management. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5168

2 1

[PATCH v26 0/4] MR4661: gdiplus: Implement Gdiplus effects
by Vijay Kiran Kamuju (＠infyquest) Feb. 26, 2024

Feb. 26, 2024

Implement few effect related functions in Gdiplus. -- v26: gdiplus: Add GdipSetEffectsParameters implementation. gdiplus: Add GdipGetEffectParameterSize implementation. gdiplus: Add GdipCreateEffect implementation. include: Add gdiplus effect parameter structs. https://gitlab.winehq.org/wine/wine/-/merge_requests/4661

5 14

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

Feb. 26, 2024

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) Feb. 26, 2024

Feb. 26, 2024

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