May 2024 - wine-gitlab

[PATCH 0/3] MR5643: winebus: Implement Sony controllers report fixups for the iohid backend.
by Rémi Bernon (＠rbernon) 14 May '24

14 May '24

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

3 4

[PATCH v6 0/6] MR5632: Draft: Debugging testbot keyboard layouts
by Alexandros Frantzis (＠afrantzis) 14 May '24

14 May '24

-- v6: WIP: debugging layouts https://gitlab.winehq.org/wine/wine/-/merge_requests/5632

3 7

[PATCH 0/8] MR5640: odbc32: Add Wow64 thunks
by Hans Leidekker (＠hans) 14 May '24

14 May '24

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

3 9

[PATCH v5 0/6] MR5632: Draft: Debugging testbot keyboard layouts
by Alexandros Frantzis (＠afrantzis) 14 May '24

14 May '24

-- v5: WIP: debugging layouts https://gitlab.winehq.org/wine/wine/-/merge_requests/5632

3 7

[PATCH 0/1] MR5635: ntdll: Allocate crit section debug info by default for Windows versions before 8.
by Paul Gofman (＠gofman) 13 May '24

13 May '24

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=56661 Diablo II (at least with Project Diablo 2 mod) regressed with commit 8b3944e1341baaf693927c8b758851d2dbba725a ("ntdll: Only allocate debug info in critical sections with RTL_CRITICAL_SECTION_FLAG_FORCE_DEBUG_INFO."). I debugged that and found that a mod's DLL checks for the debug info presence specifically, and that works on modern Windows only because the game has compat shim enabled through Windows Compatibility Database ("AllocDebugInfoForCritSections"). I know that depending the behaviour on the Win version set in winecfg is not much favoured, but we have a couple of examples of that (e. g., kernelbase/file.c: CreateFileA()). So since this is a core part which changed behaviour on Windows but received a compatibility shim we may do so in this case. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/5635

3 2

[PATCH v4 0/6] MR5632: Draft: Debugging testbot keyboard layouts
by Alexandros Frantzis (＠afrantzis) 13 May '24

13 May '24

-- v4: WIP: debugging layouts https://gitlab.winehq.org/wine/wine/-/merge_requests/5632

3 7

[PATCH v3 0/6] MR5632: Draft: Debugging testbot keyboard layouts
by Alexandros Frantzis (＠afrantzis) 13 May '24

13 May '24

-- v3: WIP: debugging layouts https://gitlab.winehq.org/wine/wine/-/merge_requests/5632

3 7

[PATCH v2 0/6] MR5632: Draft: Debugging testbot keyboard layouts
by Alexandros Frantzis (＠afrantzis) 13 May '24

13 May '24

-- v2: WIP: debugging layouts https://gitlab.winehq.org/wine/wine/-/merge_requests/5632

3 7

[PATCH 0/6] MR5632: Draft: Debugging testbot keyboard layouts
by Alexandros Frantzis (＠afrantzis) 13 May '24

13 May '24

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

3 7

[PATCH v3 0/5] MR5601: Numpad key handling in winewayland.drv (and more generally for drivers using KBDTABLES)
by Alexandros Frantzis (＠afrantzis) 13 May '24

13 May '24

This MR improves the handling of numpad keys for drivers using KBDTABLES (only the Wayland driver at this point). It achieves this by: 1. Allowing drivers to send only the scancode in keyboard events, with win32u performing the scan->vkey mapping internally. A nice side effect of this change is that it fixes a few user32 input test TODOs. 2. Enhancing wineserver to read extended KBD vkey attributes and perform numpad key mapping depending on modifier state. 3. Providing default VK_NUMPAD* -> WCHAR mappings in win32u. -- v3: winewayland.drv: Populate vkey to wchar entry for VK_DECIMAL. server: Send numpad virtual keys if NumLock is active. win32u: Store the full KBD vkey information in kbd_tables_init_vsc2vk. win32u: Allow drivers to send only the scan code for keyboard events. https://gitlab.winehq.org/wine/wine/-/merge_requests/5601

3 6

2025

2024

2023

2022

wine-gitlab May 2024