mirror of
https://github.com/DeeJanuz/frametop.git
synced 2026-10-07 17:00:13 +02:00
DeeJanuzandClaude Opus 5.5
82fbc6fc1b
reference.md's ft-screens keys paragraph, the relay's top docstring and hazards.md's key releases section now say that a mouse button passed through as a key in pointer mode goes to the screen the pointer is on, not where typing goes, only while one shows and Frametop isn't paused, that ft-screens lets its release through and releases it itself when the pointer leaves the screens, its screen hides, or Frametop pauses, and that a relay that starts releases mouse buttons too. hazards.md adds that the button still reaches the virtual mouse, which gamescope reads, and that a keyboard's media keys come from its Consumer Control node, which stays ungrabbed, so they reach gamescope as well as the desktop even while typing goes to the desktop. design.md says why the buttons follow the pointer: as keys, a release was lost whenever typing moved, and wlroots counts presses per button. reference.md names scripts/test-relay-buttons.sh, and keys-test's wider scope. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>