DeeJanuzandClaude Opus 5.5 18aa0fec3a Put clicks where the cursor is on scaled desktop screens ...

With a screen's scale set to anything but 100%, clicks landed away from
the cursor, further off the further from the top left (#3). ft-screens
hands KWin panel positions in buffer pixels, and KWin's nested Wayland
backend (6.2.5, WaylandInputDevice) adds surface coordinates to its
output's logical position without dividing by the output's scale. At
125% a click at the middle of a 3440x1440 screen, (1720, 720), reached
KWin as logical (1720, 720), pixel (2150, 900).

ft-screens now keeps a scale per screen and divides pointer positions by
it. ft-layout sends each screen's scale, as KWin reports it after
applying, with a new "scale N s" command, whenever it applies scales:
at desktop start and from Frametop Display Settings. Screens default to
1, so an ft-layout that never sends it keeps the old behaviour.

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

2026-09-28 21:33:03 -06:00

..

ft_layout.py

Put clicks where the cursor is on scaled desktop screens

2026-09-28 21:33:03 -06:00

ft-layout

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

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