mirror of
https://github.com/DeeJanuz/frametop.git
synced 2026-10-14 17:00:52 +02:00
DeeJanuzandClaude Opus 5.5
1fdd6f0e78
For reports like "windows won't drag while the Steam menu is open" and "Frametop's keyboard doesn't open", the report now has: - A section on the keyboard and the Steam menu: the Keyboard setting, the relay's devices (a pass-through keyboard keeps ours closed by default), ft-textinput and KWin's input method, the desktop's QT_IM_MODULE and GTK_IM_MODULE, ft-screens' state and new debug line, the SteamVR overlays shown, and the matching log lines. - --watch [SECONDS]: after the report, it records ft-screens' debug line whenever it changes, and the logs, while the user makes it happen. - A release's version and container (it reported "container dev: missing"), the gaze, desktop, eye grabber and Bluetooth units, and the newest SteamVR start rather than the log's first. ft-screens: a "debug" command (Steam menu, Steam in front, our keyboard shown or aside, mode, lasers, held press and which laser, drags in progress, where typing goes), and log lines when a drag starts, ends, or can't start, when Steam comes in front or goes, and when a requested keyboard doesn't open. The relay logs why a focused text field did or didn't open the keyboard, once per decision (keys-test covers it). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>