January 2024 - wine-gitlab

Re: [PATCH v10 0/4] MR559: vkd3d-shader/ir: Validate block-based CF, part 2. - approved
by Alexandre Julliard (＠julliard) 23 Jan '24

23 Jan '24

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

1 0

[PATCH 0/1] MR4923: winemac.drv: Detect active handwriting and panel IMEs.
by Tim Clem (＠tclem) 23 Jan '24

23 Jan '24

Allows such IMEs that process keyboard input to do so. For instance, fixes backspace and escape for handwriting methods. Unfortunately there doesn't seem to be a way to detect the activation of non-keyboard IMEs, so this needs to be checked per-keystroke. Some rough benchmarking shows that it adds about 15 microseconds of overhead, which is somewhat dwarfed by the ~50 microseconds for the dispatch to the main thread, which was always already happening. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4923

4 3

[PATCH v22 0/4] MR4661: gdiplus: Implement Gdiplus effects
by Vijay Kiran Kamuju (＠infyquest) 23 Jan '24

23 Jan '24

Implement few effect related functions in Gdiplus. -- v22: gdiplus: Add GdipSetEffectsParameters implementation. https://gitlab.winehq.org/wine/wine/-/merge_requests/4661

4 6

Re: [PATCH v2 0/1] MR4834: ntdll: NtQuerySystemInformation(SystemProcessorPerformanceInformation) fix return value
by Alexandre Julliard (＠julliard) 23 Jan '24

23 Jan '24

> It looks like before Vista it returned `STATUS_SUCCESS` which is current Wine implementation, but since Vista it started to return `STATUS_INFO_LENGTH_MISMATCH` instead Is there an actual app that depends on this? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4834#note_58683

1 0

[PATCH v21 0/4] MR4661: gdiplus: Implement Gdiplus effects
by Vijay Kiran Kamuju (＠infyquest) 23 Jan '24

23 Jan '24

Implement few effect related functions in Gdiplus. -- v21: gdiplus: Add GdipSetEffectsParameters implementation. https://gitlab.winehq.org/wine/wine/-/merge_requests/4661

3 5

[PATCH 0/1] MR4922: mshtml: Implement document.lastModified.
by Gabriel Ivăncescu (＠insn) 23 Jan '24

23 Jan '24

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

3 2

[PATCH 0/3] MR594: vkd3d-shader/ir: Move some more fields from struct vkd3d_shader_desc to struct vsir_program.
by Henri Verbeet (＠hverbeet) 23 Jan '24

23 Jan '24

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

2 3

[PATCH 0/5] MR593: vkd3d: Use debugstr_hresult() in device.c and resource.c.
by Henri Verbeet (＠hverbeet) 23 Jan '24

23 Jan '24

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

2 5

Re: [PATCH v20 0/4] MR4661: gdiplus: Implement Gdiplus effects
by Vijay Kiran Kamuju (＠infyquest) 23 Jan '24

23 Jan '24

On Tue Jan 23 16:39:13 2024 +0000, Esme Povirk wrote: > Now that I'm looking closer, I'm even more confused. As far as I can > tell from the tests, the parameter size of RedEyeCorrectionEffect should > always be sizeof(RedEyeCorrectionEffect). So, why does > GdipGetEffectParameterSize return something different? > And if a different size is allowed to be passed in, there should be > tests for it. I have tested it, it always includes the size of the numareas. I have tested it, it throws InvalidParameter errors. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4661#note_58668

1 0

Re: [PATCH v20 0/4] MR4661: gdiplus: Implement Gdiplus effects
by Esme Povirk (＠madewokherd) 23 Jan '24

23 Jan '24

On Tue Jan 23 16:34:02 2024 +0000, Esme Povirk wrote: > I don't see anything changed that would address this. Now that I'm looking closer, I'm even more confused. As far as I can tell from the tests, the parameter size of RedEyeCorrectionEffect should always be sizeof(RedEyeCorrectionEffect). So, why does GdipGetEffectParameterSize return something different? And if a different size is allowed to be passed in, there should be tests for it. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/4661#note_58667

1 0

2025

2024

2023

2022

wine-gitlab January 2024