dtourolle
048d48f532
Every scene was recorded again on a release build of this commit with the automation feature. Master changed what nearly every picture shows after they were taken: scrollbars on the develop column, the grid, the sidebar and Settings; a "?" beside Settings in develop's top bar, with its controls regrouped; the Film row opening its list as a popup. The film scene pressed the list's rows through the develop column, which no longer holds them: the list is a popup, and the automation hook reports its contents relative to it. The scene now opens it with film_list_open, turns the wheel down it and back so the popup and its scrollbar are seen scrolling, and clicks Velvia at its popup position plus the popup's origin. The caption says so. film_reach passed in the same run: the last stock was reached by the wheel, a drag, the scrollbar and the keys. Looked at as contact sheets of each GIF's middle and last frames and each PNG. launch, launch-folder, library-nesting.png and library-collection-menu came out byte-identical after optipng and are unchanged. develop-zoom's deepest frames are smooth on Xvfb as before; its caption does not claim blocks. Settings shows version 0.15.0, the build's own, until the release commit bumps it.
tools/manual — the pictures in docs/manual
record.sh drives the desktop build on a private X server and records the
scenes in scenes.py into docs/manual/media/:
tools/manual/record.sh /var/tmp/dr-demo/library # every scene
tools/manual/record.sh /var/tmp/dr-demo/library develop_zoom # one, and what it needs
tools/manual/record.sh --changed /var/tmp/dr-demo/library # those whose sources moved
tools/manual/record.sh --check # the manual and the scenes agree
tools/manual/record.sh --list
Set DR_LIBRARY_SNAPSHOT to a pristine copy of the library: a recording
rates, files and merges, and the snapshot is copied over the library first.
Each run starts from a fresh profile under DR_HOME.
Controls by name
The binary is built with --features automation, which lets the app answer
"where is the control labelled Exposure?" over the Unix socket named by
DR_AUTOMATION (ui/dr-ui/src/automation.rs). No other build has the
feature, and a build that has it listens only when the variable is set. The
names are the accessible labels a screen reader reads, so a scene says
click_on('Select@Button') or slide('Exposure', 24) rather than a pixel,
and survives a panel that moves. The pointer itself is still xdotool.
DR_HOME=/var/tmp/x tools/manual/drive.py launch /some/folder # a feature build in DR_BIN
tools/manual/drive.py labels # every name on screen
tools/manual/drive.py click-on 'Settings@Button'
tools/manual/drive.py ids canvas # things with no name: id:canvas-image
tools/manual/drive.py stop
Grid cells are named by file (_MG_8393@ListItem), rating stars 1 star
to 5 stars. What a scene cannot name — a point on the photograph, the crop
rectangle's corner — it places relative to something it can
(drive.photo(fx, fy), id:move-area).
Scenes and the manual
Each scene in scenes.py declares the pictures it makes, as the manual names
them, and the globs of the sources that could change them. --check fails
when the manual shows a picture no scene makes, or a scene makes one the
manual does not show; it reads two files and runs in CI. --changed
re-records a scene when one of its sources, or its own code, has changed
since the commit that last touched its pictures.
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.