Default Escape release can restore mouse capture after a later F1 menu #2031

Closed

opened 2026-11-11 00:34:27 +00:00 by Arkex-ai · 0 comments

Arkex-ai commented

2026-11-11 00:34:27 +00:00

(Migrated from github.com)

I reproduced the sequence with the actual Windows Escape and menu-capture routines at d9263175, using mocked window APIs. The host remembers an Escape release even when that key did not open the menu. The control where Escape does open the menu restored capture as intended.

I will check both hosts and preserve normal capture restoration when a menu actually interrupted it. S3, affected share unknown, confidence 1.0 for the Windows host fixture. Native game testing is pending. Follow-up to #1998. Claim in #dev-work.

With the default Insert/F1 shortcut, Escape releases a captured mouse. If you then open the Hookshot menu with F1 and close it without clicking in the game, the mouse can be captured again unexpectedly. I reproduced the sequence with the actual Windows Escape and menu-capture routines at `d9263175`, using mocked window APIs. The host remembers an Escape release even when that key did not open the menu. The control where Escape does open the menu restored capture as intended. I will check both hosts and preserve normal capture restoration when a menu actually interrupted it. S3, affected share unknown, confidence 1.0 for the Windows host fixture. Native game testing is pending. Follow-up to #1998. [Claim in #dev-work](https://discord.com/channels/1568810484818378804/1569019786766188665/1569872816155660440).

Commenting is not possible because the repository is archived.