Two changes to the unattended path, both prompted by deploying to the rack.
The autostart can win the race against USB enumeration at boot, so the panel
may simply not exist yet when socktop-swipe starts. Opening it now retries for
ten seconds -- long enough for enumeration, short enough that a genuinely wrong
device path still reports promptly.
If the panel cannot be opened at all, `run` no longer treats that as fatal. By
that point the dashboard is already on the wall, and exiting would replace a
display you cannot swipe with no display at all. It now says loudly that
gestures are inactive, points at the movement subcommands, and carries on
serving the control socket. `daemon` and `doctor` still fail fast, since there
is no display at stake in either.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Two bugs found deploying to the LattePanda, both of which v1 also had.
Window options do not propagate from the session and new windows do not
inherit them. `set-option -t <session> pane-border-status` quietly applies to
whichever window happens to be current, so only ONE window ever got pane
borders -- v1's rack display has had unlabeled borders on two of its three
windows this whole time and nobody noticed, because the window that got them
was the one usually on screen. This is the same trap that makes remain-on-exit
useless here. pane-border-status, pane-border-format and allow-rename are now
set per window in place(), and a test asserts every window has them.
Pane labels no longer use `select-pane -T`. The pane *title* is writable by
whatever runs in the pane: unifly probes for Kitty graphics support on startup
and tmux consumed part of that probe as a title change, so the border read
"Gi=31,s=1,v=1,a=q,t=d,f=24;AAAA" instead of "unifly". Labels now live in a
pane-scoped user option, @socktop_label, which no escape sequence can reach;
pane-border-format falls back to the title if it is somehow unset.
Also: `terminal:` now expands a leading ~/ like `binaries:` already did. A
window manager's PATH rarely includes ~/.cargo/bin, so a full path is the usual
answer there and should not have to be spelled out longhand.
Build cost corrected from guesses to measurements on the LattePanda (Atom
x5-Z8350, 4 cores, 1.9 GB, no swap, toolchain already present): 108 seconds,
peak 1.1 GB, 103 MB target directory, 946 KB binary. The README said twenty
minutes and the installer budgeted 600 MB; both were wrong.
Integration tests now use one tmux session name each -- cargo runs them in
parallel and they were tearing down each other's server state.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Installer rewritten around a preflight: distro, package manager, display
manager, window manager, terminal, tmux, cargo, git, screen locker, touch
device, device permissions and free disk are all checked BEFORE anything is
installed, and the total cost is printed once for a single confirmation.
Prompts read /dev/tty so they still work when the script is piped from curl,
and fall back to defaults with a notice when there is no terminal at all.
Several "[ test ] && action" statements were set -e landmines: under set -e an
AND-OR list that ends up false aborts the script, so a box with no lightdm, no
i3 or nothing to install would have exited silently partway through detection
-- which is exactly the fresh-Debian case the installer exists for. Rewritten
as if-statements and verified against a stripped PATH with no tmux, cargo, git
or package manager present. Also fixed cargo detection reporting blank instead
of NOT INSTALLED: the status of `cargo --version | cut` is cut's, and cut
succeeds on empty input, so the fallback never fired.
Device access now defaults to a udev rule matching touchscreens only, rather
than the input group, which grants access to every input device including the
keyboard and needs a full logout.
README rewritten for someone who has not seen the project: what the photo
shows, the hardware, install, then a config built up step by step, each step
with the YAML and the resulting map. Every example is verified verbatim
against the binary, and every relative link resolves. The mechanism and the
reasoning move to notes/: DESIGN.md, HARDWARE-NOTES.md, V1-BASH.md, TODO.md.
cad/README.md was a verbatim copy of the one inside
geeekpi_rack_adapter_release_v1/, so every path in it -- including the
screenshot -- was broken from where it sits. Corrected to its own level, and
it now states once that the 9-inch screen, the 10-inch mini-rack mount and the
19-inch rack are three different measurements.
The v1 shell implementation is removed; it stays recoverable at tag v1.2 and
notes/V1-BASH.md carries the setting-by-setting migration table.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Replaces the three shell scripts' logic with one binary. tmux stays the
pane engine; src/session/ is the only module that knows that.
The grid model: coordinates are sparse ordinals, so only their sort order
matters and a socktop group is one cell however many hosts it holds.
Horizontal movement walks a cell's sub-sequence (tiled overview, then each
host zoomed) and leaves only after the last one; entry direction decides
whether you land on the first or last sub-screen. Vertical movement returns
to where you were in that row, and snaps to the nearest column only on the
first visit.
Notable details found while building:
* Unquoted "at: 0x0" is hexadecimal 0 to YAML, and "1x0" is not valid hex,
so only the row-0 entries would break. Deserialization catches the integer
case and names the fix.
* Panes are addressed by tmux id, never index, and each command is wrapped
so the pane outlives it. v1's remain-on-exit cannot do this: it is a
per-window option that new windows do not inherit, so a monitor that exits
during construction destroys its window and the next split fails with
"no current target". Now a dead monitor stays on screen with its status.
* Contact-count averaging, not summing: a panel reporting one finger as
three contacts must not look like three times the travel.
* Movement subcommands wait for the move to happen and report where they
landed, so they are scriptable rather than fire-and-forget.
36 tests: the grid model, the gesture classifier and an end-to-end pass
against a real tmux server.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
jasonwitty