Game: dialogue pointer handling overrides assigned mouse-button actions #85

New issue

Open

opened 2026-11-13 02:27:27 +00:00 by mooki · 0 comments

mooki commented

2026-11-13 02:27:27 +00:00

Longshot version

Carried from Hookshot v2.1.0. The same pointer/input policy remains in Longshot main 6b2dafefe; no native Windows game was run for this move.

What kind of problem

Controls

What happened

ligmajammin reported that mouse bindings behave differently when a dialogue presents choices. Their listed setup binds A to right-click and Y to left-click. Left-click exposes the pointer instead of consistently selecting the focused choice, and using Y to advance ordinary dialogue opens the dialogue-history view. The narrative also calls right-click B, so the exact saved setup is not known.

The GitHub report was closed as a duplicate of the input tracker, not because a fix landed. Neither has a corresponding Longshot issue.

I traced and exercised the Windows handlers in game-free checks. Captured left-click delivers its Y binding. In pointer mode mouse bindings are suppressed; clicking a choice delivers A and right-click delivers B regardless of its binding. These rules remain in Longshot's input path and pointer handler.

The open decision is whether an explicitly assigned mouse action should take priority in dialogue choices, and how to distinguish it from the shipped default. A blanket binding-first change would remove existing point-and-click behavior; Y must not silently become A. No speculative remap was made. E still confirms and was the reporter's workaround. The conversation itself has not been reproduced on Windows here.

Where in the game

Kokiri Forest, the first conversation with Saria sitting on the log; dialogue choices and history.

How often

Every time in the original report; handler behavior reproduced in source checks, not a Windows game.

Graphics card and driver version

Reporter: Radeon RX 9070 XT, described as the latest driver without a version number.

CPU, RAM and operating system

Reporter: Ryzen 7 2700X, 32 GB RAM, Windows 11 IoT LTSC.

Changes from the defaults

A=right-click, B=Space, X=Shift, Y=left-click, ZL=I through a mouse macro; instant text speed. The two original log attachments remain linked from the report.

Other software hooked into the game

The form says none. The reporter also describes a mouse macro; its software and implementation were not supplied.

Reported on GitHub as NotRexed/Hookshot#2597; taken on there by mooki.

### Longshot version Carried from Hookshot v2.1.0. The same pointer/input policy remains in Longshot main `6b2dafefe`; no native Windows game was run for this move. ### What kind of problem Controls ### What happened [ligmajammin reported](https://github.com/NotRexed/Hookshot/issues/2597) that mouse bindings behave differently when a dialogue presents choices. Their listed setup binds A to right-click and Y to left-click. Left-click exposes the pointer instead of consistently selecting the focused choice, and using Y to advance ordinary dialogue opens the dialogue-history view. The narrative also calls right-click B, so the exact saved setup is not known. The GitHub report was closed as a duplicate of [the input tracker](https://github.com/NotRexed/Hookshot/issues/2504), not because a fix landed. Neither has a corresponding Longshot issue. I [traced and exercised the Windows handlers in game-free checks](https://github.com/NotRexed/Hookshot/issues/2597#issuecomment-6823982156). Captured left-click delivers its Y binding. In pointer mode mouse bindings are suppressed; clicking a choice delivers A and right-click delivers B regardless of its binding. These rules remain in Longshot's [input path](https://git.magicbean.dev/MagicBeanDev/Longshot/src/commit/6b2dafefe5a5108bc1ab99deb98dab74a5ba9dd6/host/nn_hid.c#L1036-L1039) and [pointer handler](https://git.magicbean.dev/MagicBeanDev/Longshot/src/commit/6b2dafefe5a5108bc1ab99deb98dab74a5ba9dd6/host/oot_menu.c#L696-L699). The open decision is whether an explicitly assigned mouse action should take priority in dialogue choices, and how to distinguish it from the shipped default. A blanket binding-first change would remove existing point-and-click behavior; Y must not silently become A. No speculative remap was made. E still confirms and was the reporter's workaround. The conversation itself has not been reproduced on Windows here. ### Where in the game Kokiri Forest, the first conversation with Saria sitting on the log; dialogue choices and history. ### How often Every time in the original report; handler behavior reproduced in source checks, not a Windows game. ### Graphics card and driver version Reporter: Radeon RX 9070 XT, described as the latest driver without a version number. ### CPU, RAM and operating system Reporter: Ryzen 7 2700X, 32 GB RAM, Windows 11 IoT LTSC. ### Changes from the defaults A=right-click, B=Space, X=Shift, Y=left-click, ZL=I through a mouse macro; instant text speed. The two original log attachments remain linked from the report. ### Other software hooked into the game The form says none. The reporter also describes a mouse macro; its software and implementation were not supplied. Reported on GitHub as NotRexed/Hookshot#2597; taken on there by mooki.