- wine-gitlab - winehq.org

[PATCH 0/3] MR94: Fix other synchronization problems
by Giovanni Mascellani (＠giomasce) 24 Feb '23

24 Feb '23

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

3 8

[PATCH v7 0/2] MR2262: winspool: Check dmSize in IsValidDevmodeW
by Tingzhong Luo (＠tzluo) 24 Feb '23

24 Feb '23

When dmSize is zero or greter than size of input buffer, `IsValidDevmodeW()` failed in Windows 10. But current implementation in wine, it will return `true` because there is no check to `dm.dmSize`. -- v7: winspool: Check the alignment of dmSize in IsValidDevmodeW() https://gitlab.winehq.org/wine/wine/-/merge_requests/2262

3 2

[PATCH v6 0/2] MR2262: winspool: Check dmSize in IsValidDevmodeW
by Tingzhong Luo (＠tzluo) 24 Feb '23

24 Feb '23

When dmSize is zero or greter than size of input buffer, `IsValidDevmodeW()` failed in Windows 10. But current implementation in wine, it will return `true` because there is no check to `dm.dmSize`. -- v6: winspool: Check the alignment of dmSize in IsValidDevmodeW() https://gitlab.winehq.org/wine/wine/-/merge_requests/2262

3 2

[PATCH v5 0/1] MR2262: winspool: Check dmSize in IsValidDevmodeW
by Tingzhong Luo (＠tzluo) 24 Feb '23

24 Feb '23

When dmSize is zero or greter than size of input buffer, `IsValidDevmodeW()` failed in Windows 10. But current implementation in wine, it will return `true` because there is no check to `dm.dmSize`. -- v5: winspool: Check dmSize in IsValidDevmodeW https://gitlab.winehq.org/wine/wine/-/merge_requests/2262

4 4

[PATCH 0/1] MR109: vkd3d-shader/hlsl: Improve handling of builtin alias type "matrix".
by Nikolay Sivov (＠nsivov) 24 Feb '23

24 Feb '23

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

2 1

[PATCH 0/1] MR2268: oleaut32: Allocate a full pointer when unmarshalling byref arrays.
by Rémi Bernon (＠rbernon) 24 Feb '23

24 Feb '23

Instead of the 4 bytes array wire size returned by get_type_size, which will truncate the pointer on 64-bit. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=54562 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2268

3 2

[PATCH 0/1] MR2253: gdi32/tests: add some last error checks
by Ivan Chikish (＠nekotekina) 24 Feb '23

24 Feb '23

Related bug report: #54405 The game engine (FVP) does compare GetGlyphOutlineA result with zero and checks GetLastError in that case. Maybe I'm missing something but I believe the last error shouldn't be set for "empty" characters. I don't know why it was omitted in tests. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2253

3 2

[PATCH 0/5] MR2038: server: Track cursor handle and window changes.
by Rémi Bernon (＠rbernon) 24 Feb '23

24 Feb '23

The idea here is to track the cursor changes on the server side, ultimately [1] using a private message to notify user drivers of changes to apply, instead of tracking the changes in user drivers with throttle mechanisms. This would greatly simplify winex11 mouse message handling as we would not need to try syncing the window cursor on every mouse move, and ultimately it would also make it possible to have a single thread listening to input in the background. Currently the input thread needs to own the windows that are under the cursor to be able to set it. Having a single input thread (per-process at least, but ideally and ultimately per-prefix), will solve several issues with input not being received when the foreground thread isn't actively checking their message, as well as issues with DInput incorrectly checking window messages when it should not. [1] See https://gitlab.winehq.org/rbernon/wine/-/merge_requests/8/commits -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2038

3 9

[PATCH 0/1] MR1240: gitlab: Run related tests on every commit.
by Rémi Bernon (＠rbernon) 24 Feb '23

24 Feb '23

This restores the feature we had with the testbot running related on intermediate commits, though it only does it on Linux and it would be nice to have it on Windows too. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/1240

2 2

[PATCH 0/5] MR2062: winex11: Expose supported and configured keyboard layout in winecfg.
by Rémi Bernon (＠rbernon) 24 Feb '23

24 Feb '23

This adds a new Input tab to winecfg, moving the mouse grab settings there. Then this makes winex11 keyboard layout detection configurable as well, allowing the user to override the keyboard layout detection if for some reason it was incorrect. This isn't solving anything yet, but I then intend to make keyboard scancode detection configurable as well, and optional. As I described in https://www.winehq.org/pipermail/wine-devel/2020-October/175641.html, I believe that X11 keyboard keycode to scancode mapping is most of the time a fixed mapping, except in some rare cases. Trying to detect it from the keyboard layout will never work reliably, especially nowadays where keyboard layouts are completely made up from Linux IME (for instance a GNOME language settings with up to four keyboard layouts translates to a single Xkb mapping using groups for each layout). The X11 keycode are remapped only in some more rarely used implementations, such as XVNC and we should try to detect it only in such cases. Many Windows applications are depending on accurate scancodes, and making the mapping detection optional (and disabled by default) will solve all the issues we have in the most common case (https://bugs.winehq.org/show_bug.cgi?id=30984, https://bugs.winehq.org/show_bug.cgi?id=45605). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2062

2 7

2025

2024

2023

2022

wine-gitlab