Files
DarkRoom/tools/manual
dtourolle 5b4ad11853
Benchmarks / CPU and I/O (per commit) (push) Failing after 6m16s
Benchmarks / Frame budget (on demand) (push) Skipped
Build and test / Desktop (Linux) (push) Failing after 42s
🐳 Android image / Build and push (push) Successful in 1s
Build and test / android-image (push) Successful in 1s
🐳 Windows image / Build and push (push) Successful in 1s
Build and test / windows-image (push) Successful in 2s
Build and test / Layer separation (push) Successful in 26s
Traceability / Requirement traces (push) Failing after 38s
Build and test / Android (aarch64) (push) Failing after 2m20s
Build and test / Windows (x86_64, cross) (push) Failing after 3m3s
Manual: nested collections, and the ghost drawn as it should be
A scene that makes a parent, nests two collections in it by drag and by
the menu, files frames into a child and opens the parent to see it count
both; stills of the tree and of the menu. The collections recording is
re-made now that the bitmap under the cursor is the photograph.

drive.py grows a multi-leg drag: a diagonal with much vertical in it is
taken by the grid's Flickable as a scroll before the DragArea can claim
it, so a drag to the sidebar goes sideways first.
2026-09-20 16:27:18 +02:00
..

tools/manual — the pictures in docs/manual

record.sh <library> drives the desktop build on a private X server and records every scene in scenes.py into docs/manual/media/. drive.py is the puppeteer underneath — launch, click, drag, type, screenshot, record — and is usable on its own to look at a panel after changing it:

DR_HOME=/var/tmp/x tools/manual/drive.py launch /some/folder
tools/manual/drive.py click 1543 22        # Settings
tools/manual/drive.py shot /tmp/settings.png
tools/manual/drive.py stop

The demo library is the author's: seventy frames with no people in them, the fixtures/pano set among them. The scenes' cell coordinates are for that grid, at 1600×1100; the panel coordinates hold for any library.

Two things the scripts know that are not obvious: a Slint TouchArea wants a held press, not xdotool's click; and the app is driven on Xvfb rather than the desktop because under XWayland at scale 2 a pointer warp lands at twice the coordinate asked for.