DeeJanuzandClaude Opus 5.5 4828dd46b5 Pointer: a release never wakes the pointer ...

Any "btn" or "scroll" from the relay woke a pointer that was off. When
Frametop pauses for a game, the relay's stand_down sends the releases of
the clicks held into the pause, and with its pointer already off (the
idle timeout or pointer_toggle during a press) it used to send them with
no "hide" after. The helper woke on them, connected the virtual
controller and took the right hand role during the game.

Now a button release or a scroll back to 0 0 doesn't wake it. The
release is still handled as before (it ends its press, or goes to the
driver), so the driver doesn't reconnect later with the button down.
Outside a pause this changes one case: a mouse button let go after a
moving controller released the pointer mid-press. That release used to
reconnect the controller, recenter it and release there; now it updates
the disconnected controller, and ft-screens still gets its "up".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-05 16:51:09 -06:00

..

common

Frametop: a multi-screen desktop and universal 3D mouse for the Steam Frame

2026-09-26 16:14:13 -06:00

driver

SteamVR's tools find SteamVR from a terminal in the Frametop desktop

2026-10-05 10:53:59 -06:00

helper

Pointer: a release never wakes the pointer

2026-10-05 16:51:09 -06:00

probe

Frametop: a multi-screen desktop and universal 3D mouse for the Steam Frame

2026-09-26 16:14:13 -06:00