You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When mouse grab is released, the mouse cursor re-appears, but if you have multiple screens it will not be able to leave the current screen until you can focus a window besides RetroArch.
This is likely specific to the Windows mouse ungrab implementation.
Expected behavior
When mouse grab is released, the released mouse cursor should be able to move to another screen.
Actual behavior
When mouse grab is released, the mouse cursor is confined to the current screen while RetroArch remains focused.
Steps to reproduce the bug
Start portable Retroarch, default settings, should be windowed.
Launch any game.
Press F11 to grab the mouse.
Press F11 to ungrab the mouse.
Observe that the mouse cursor is now trapped inside the current monitor screen.
Bisect Results
Has been present since at least 1.16.0. but probably goes much further back. (I would guess 1.9.1 based on the blame of the relevant code.)
Version/Commit
RetroArch: 1.17.0 (64-bit Windows)
Environment information
OS: Windows 10
Drivers: (should be default)
Menu: ozone
Video: d3d11
Input: dinput
The text was updated successfully, but these errors were encountered:
If turning mouse grab off, ClipCursor should use a NULL parameter. Instead of releasing the mouse, we've used GetDesktopWindow() to create a confinement to the current screen.
Description
When mouse grab is released, the mouse cursor re-appears, but if you have multiple screens it will not be able to leave the current screen until you can focus a window besides RetroArch.
This is likely specific to the Windows mouse ungrab implementation.
Expected behavior
When mouse grab is released, the released mouse cursor should be able to move to another screen.
Actual behavior
When mouse grab is released, the mouse cursor is confined to the current screen while RetroArch remains focused.
Steps to reproduce the bug
Bisect Results
Has been present since at least 1.16.0. but probably goes much further back. (I would guess 1.9.1 based on the blame of the relevant code.)
Version/Commit
Environment information
The text was updated successfully, but these errors were encountered: