aboutsummaryrefslogtreecommitdiffstats
path: root/window-switcher/Switcher.qml
AgeCommit message (Collapse)AuthorFilesLines
26 hoursfeat(window-switcher): the grid, the selection, and an empty stateDanilo M.1-8/+100
Columns are the window count capped at six and the grid centres, so one card sits dead centre and two straddle the middle. Cards grow to fill their row up to 640px: without a ceiling a lone preview becomes a full-screen mirror of the window it stands for. The close button leaves the overlay open, because closing is a side errand and a dismissal would mean reopening to close a second window. That makes an empty overlay reachable by closing the last window, so there is an empty state rather than a full-screen dim with nothing in it, which reads as a hang. The selection needs no reset. The LazyLoader destroys the overlay on close and constructs a new one on the next opening, verified with a build counter: two openings, two constructions. selectedIndex is therefore 0 on every showing by initialisation, and an explicit assignment in Component.onCompleted would be a no-op. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SYg4wYHq5XNbiVmMeKRb1S
27 hoursfix(window-switcher): pick the screen the way the other components doDanilo M.1-1/+4
The screen was found by a name written inline, falling back to null. The other three panels all take a monitor property and fall back to screens[0], so this now does too: a machine without a DP-1 gets its first monitor rather than a null screen, and the name is in one place if it ever needs changing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SYg4wYHq5XNbiVmMeKRb1S
27 hoursfeat(window-switcher): the overlay skeleton, and a proven EscapeDanilo M.1-0/+82
A fifth component, so the same keepalive window as the other four: a config with no visible window exits without reporting anything, and this overlay is hidden almost always. Escape is handled on a focused Item inside the PanelWindow rather than on the window, because key events reach a focused item and Keys.onEscapePressed on a PanelWindow never fires. Proven before the grid is built on top of it, since keyboard navigation depends on the same grab. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SYg4wYHq5XNbiVmMeKRb1S