With this commit we proof that PixelOffsetMode None and Fast
is implemented correctly.
By changing colour of second pixel of bitmap Source,
the issues with pixel offset appear
for PixelOffsetMode Half and HighQuality.
Extending tests is starting point for further
improvements of implementation pixel offset modes
to match implementation from native gdiplus.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/3774
If lparam is null, the current code crashes when it hits the memcpy in pack_user_message.
--
v2: win32u: Correct the packed size of WM_GETDLGCODE when lparam is NULL.
win32u: Add a test for cross-process WM_GETDLGCODE with a NULL lparam.
https://gitlab.winehq.org/wine/wine/-/merge_requests/3755
I wanted to use ._xy element access to make it shorter, but that attempt was crushed by the reality - such indexing apparently compiles but does not produce correct element access loads. I'm going to update once this is fixed.
--
v3: vkd3d-shader/hlsl: Add determinant() function.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/329
--
v2: mshtml: Use query_interface in the dispex vtbl for HTMLPluginsCollection.
mshtml: Use query_interface in the dispex vtbl for HTMLNamespaceCollection.
mshtml: Use query_interface in the dispex vtbl for HTMLMimeTypesCollection.
mshtml: Use query_interface in the dispex vtbl for HTMLAttributeCollection.
mshtml: Use query_interface in the dispex vtbl for HTMLFiltersCollection.
mshtml: Use query_interface in the dispex vtbl for HTMLRectCollection.
mshtml: Use query_interface in the dispex vtbl for HTMLElementCollection.
mshtml: Use query_interface in the dispex vtbl for HTMLDOMChildrenCollection.
mshtml: Use query_interface in the dispex vtbl for StyleSheetRules and
mshtml: Use query_interface in the dispex vtbl for CSS Styles.
mshtml: Use query_interface in the dispex vtbl for HTMLStorage.
mshtml: Use query_interface in the dispex vtbl for HTMLLocation.
mshtml: Use query_interface in the dispex vtbl for builtin constructors.
https://gitlab.winehq.org/wine/wine/-/merge_requests/3773
This MR adds support for handling `wl_pointer` devices:
1. Handle enter/leave/(absolute) motion/button/axis events to allow users to interact with applications using such devices, e.g., a mouse.
2. Update the cursor image used for Wayland surfaces based on the Windows cursor bitmap data.
A few notes:
1. A single `wl_seat`/`wl_pointer` is supported for now.
2. Many of the input interactions require window management support that hasn't been implemented yet (e.g., popup positioning, resizing, max/fullscreen).
3. There is some potential for bad interactions between the input event dispatching mechanism and the `win32u` flushing logic for `window_surface` , which can lead to visual glitches. Although I don't think this is blocker for this MR, I would like to start a discussion about the problem and mitigation ideas in a [comment](https://gitlab.winehq.org/wine/wine/-/merge_requests/3686#note_438… below.
Thanks!
--
v2: winewayland.drv: Implement SetCursor using cursor bitmap data.
winewayland.drv: Handle pointer button and scroll events.
winewayland.drv: Handle pointer motion events.
winewayland.drv: Handle pointer focus events.
https://gitlab.winehq.org/wine/wine/-/merge_requests/3686