At least Doom 64 calls ClipCursor() with identical parameters
repeatedly, which seems to cause a considerable overhead. Together with
high polling rate mouse input this causes the game to almost freeze
while the mouse is being moved. So if the clipping did not change we can
bail out early because it will not cause any observable difference
anyway.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=46976
Signed-off-by: Jan Kl��tzke <jan(a)kloetzke.net>
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/825
As well as a few other fixes for https://gitlab.winehq.org/wine/wine/-/merge_requests/551.
--
v2: win32u: Introduce a new internal WINE_DM_UNSUPPORTED display flag.
win32u: Rename (read|write)_registry_settings to adapter_(set|get)_default_mode.
win32u: Avoid unnecessary copy of adapter path and device name.
win32u: Avoid copying the modes array in NtUserChangeDisplaySettings.
win32u: Introduce reference counting to struct adapter.
win32u: Fill the local full_mode variable instead of using the modes array.
win32u: Rename get_full_mode variables and avoid using devmode directly.
wineandroid.drv: Add missing DM_DISPLAYORIENTATION flag on display mode.
https://gitlab.winehq.org/wine/wine/-/merge_requests/814
Due to me updating to mesa-git, the gl vendor string got changed and now wine thinks it's an nvidia card, so this patch fixes it
--
v2: wined3d: Fix bug with AMD gl vendor returning nvidia
https://gitlab.winehq.org/wine/wine/-/merge_requests/826
Due to me updating to mesa-git, the gl vendor string got changed and now wine thinks it's an nvidia card, so this patch fixes it
--
v4: wined3d: Add support for renoir graphics
https://gitlab.winehq.org/wine/wine/-/merge_requests/826
This implements sending StorageEvents to the same window/doc from where the storage change happened, which seems to be a thing on native IE. For some reason I was unable to have them actually sent to other windows, so that's not implemented since I've no idea how that even gets triggered to test it, and if it does it will probably be in a follow up MR, even though that's *supposed* to be the use of these events���
localStorage sends for `onstoragecommit` on the doc that did the change, while sessionStorage sends for `onstorage` on the window and doc that did the change, depending on compat mode. Although the event sent to the document's `onstorage` seems to be a legacy/old-style event (as tests show).
Tests are on the last patch since events have to be sent properly (else it hangs).
--
v4: mshtml: Send StorageEvents to iframe windows properly.
mshtml: Don't expose document.onstorage for IE9+ modes.
mshtml/tests: Add tests for StorageEvents with parallel documents.
mshtml: Send StorageEvents when removing an existing item.
mshtml: Send StorageEvents when setting an item.
mshtml: Implement StorageEvent and send it when clearing the storage.
mshtml: Move the MessageEvent construction to a helper.
include/mshtml: Add IDOMStorageEvent and DispDOMStorageEvent interfaces.
https://gitlab.winehq.org/wine/wine/-/merge_requests/795