January 2024 - wine-gitlab

[PATCH 0/3] MR4903: user32/tests: Rewrite KEYEVENTF_UNICODE tests and add a test for LL hooks blocking behavior.
by Rémi Bernon (＠rbernon) 22 Jan '24

22 Jan '24

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

3 4

[PATCH v4 0/2] MR4251: windows.ui: Add stubs for InputPane class
by Fabian Maurer (＠DarkShadow44) 22 Jan '24

22 Jan '24

This is used by google-chrome. I added this hoping to fix an issue, but this was unrelated to input pane. Not having it doesn't seem detrimental, although since I already implemented this I figured it would be a waste to throw it away. -- v4: windows.ui: Add stubs for InputPane class include: Add Windows.UI.ViewManagement.InputPane definitions https://gitlab.winehq.org/wine/wine/-/merge_requests/4251

3 4

[PATCH v2 0/3] MR4902: oleaut32: Implement OleLoadPictureFile.
by Dmitry Timoshkov (＠dmitry) 22 Jan '24

22 Jan '24

-- v2: oleaut32: Implement OleLoadPictureFile. oleaut32: Factor out stream creation from OleLoadPicturePath. oleaut32: Do not reimplement OleLoadPicture in OleLoadPicturePath. https://gitlab.winehq.org/wine/wine/-/merge_requests/4902

2 3

[PATCH v2 0/3] MR4803: dlls/gdiplus: Assorted path changes
by David Kahurani (＠kahurani) 22 Jan '24

22 Jan '24

Signed-off-by: David Kahurani k.kahurani(a)gmail.com -- v2: dlls/gdiplus: Use path_list to path helper in GdipWidenPath. dlls/gdiplus: Use path_list to path helper in GdipFlattenPath. dlls/gdiplus: Add helper function for strictly allocating to a path https://gitlab.winehq.org/wine/wine/-/merge_requests/4803

2 3

[PATCH 0/3] MR4902: oleaut32: Implement OleLoadPictureFile.
by Dmitry Timoshkov (＠dmitry) 22 Jan '24

22 Jan '24

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

2 3

[PATCH 0/7] MR583: Draft: vkd3d-shader/dxil: SRV/UAV support part 2.
by Conor McCarthy (＠cmccarthy) 22 Jan '24

22 Jan '24

Goes atop !533. The last two commits belong to this MR. -- https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/583

2 7

[PATCH v2 0/2] MR4900: ntoskrnl: Reimplement ExAllocatePool* on top of ExAllocatePool2.
by Alex Henrie (＠alexhenrie) 22 Jan '24

22 Jan '24

Microsoft deprecated all of these functions except ExAllocatePool2 and ExAllocatePool3, so it's a safe bet that in Windows the old functions are just wrappers around the new ones now. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54362 -- v2: ntoskrnl: Reimplement ExAllocatePool* on top of ExAllocatePool2. https://gitlab.winehq.org/wine/wine/-/merge_requests/4900

2 2

[PATCH 0/2] MR4900: ntoskrnl: Reimplement ExAllocatePool* on top of ExAllocatePool2.
by Alex Henrie (＠alexhenrie) 22 Jan '24

22 Jan '24

Microsoft deprecated all of these functions except ExAllocatePool2 and ExAllocatePool3, so it's a safe bet that in Windows the old functions are just wrappers around the new ones now. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54362 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4900

2 2

Re: [PATCH v3 0/3] MR4857: Draft: gdi32,win32u: Implement D3DKMTEnumAdapters2.
by Zhiyi Zhang (＠zhiyi) 22 Jan '24

22 Jan '24

On Fri Jan 19 22:20:34 2024 +0000, Krzysztof Bogacki wrote: > Indeed, but I thought it would be safer to allocate some memory for a > temporary working area, try enumerating adapters and only copy the > result if the entire operation did not fail halfway through rather than > using the array I was passed by the caller directly and risk writing > some partially misleading garbage to it. I also wasn't sure how to > proceed in such case: if I already wrote some LUIDs and handles, should > I try to `memset(0)` them just in case or leave the data there and trust > that all callers of this API will ignore whatever was written, treating > the content as unspecified? > It's also somewhat tricky to cause Windows to fail here so I don't know > how exactly does it behave when it encounters some error internally. > Copying the full result only on full success seemed like an easy way out > that allowed me to not bother figuring this out, even if it costs an > extra allocation. > But I can revert to writing to `pAdapters` directly if you'd prefer it > that way. If an error occurs, an error code is returned and the application shouldn't use the buffer. But just to be safe, you can do a memset(0) when it fails. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4857#note_58359

1 0

Re: [PATCH v3 0/3] MR4857: Draft: gdi32,win32u: Implement D3DKMTEnumAdapters2.
by Zhiyi Zhang (＠zhiyi) 22 Jan '24

22 Jan '24

> For what it's worth, I haven't seen any adapter to report TRUE here on Windows. So it might be safer to default to FALSE instead. That's fine. You can add tests for this as well. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4857#note_58358

1 0

2025

2024

2023

2022

wine-gitlab January 2024