Wire the develop panels through globals, so a second copy is one line

Every panel in the develop column declared its inputs and its callbacks and
had `app.slint` bind each one to a property or a callback on the window root.
That is fine while a panel is drawn once. N9 draws them a second time, in the
portrait dock, and the wiring is what would have to be copied: `MaskPanel`
alone ran to forty lines of forwarding, and a callback added to one copy and
not the other compiles, renders, and simply does nothing on the layout nobody
was looking at.

So the wiring moved to Slint globals. A panel reads the global and calls the
global; Rust hooks the global instead of the window; and the instantiation in
the column is now the panel's name and a pair of braces — every one of the ten
children of the column, with no property that differs by placement left to
supply.

There is a global per panel family rather than one for all of them, and the
reason is an import cycle. Each panel's model struct — `ParamRow`, `MaskRow`,
`HistogramView` — is declared in the panel's own file, so a single global
holding `[MaskRow]` and `[ParamRow]` would have to live in a file importing
`masks.slint` and `adjust.slint` while both imported the global back, which
Slint rejects. Breaking that needs six model declarations relocated, which is a
change to the data model and not to the plumbing this is about. A global beside
the panel it serves also lets each name drop the prefix it was carrying only
because the window root is one flat namespace: `root.spot-radius` is
`Repair.radius`, and `root.peaking-on` is `Peaking.showing`.

`session.slint` is new and holds the two facts every family needs and none of
them owns: whether there is an open photograph to edit, and which mode the view
is in, with the three readings of the mode derived once instead of at each of
the dozen places that tested one. `ViewMode` moves there from `adjust.slint`,
where it was only ever a lodger.

Nothing on screen changes. What is not here: the tool rail and the status strip
still take their properties at the instantiation, because they are drawn once
and N9 does not copy them; the preset sheet's own state stays on the window,
because the library grid opens the same sheet and a global cannot bind the
window's state — which is why `Transfer.open-presets` is handled in
`presets.rs`, beside the summary it already had to compute.

docs/gestures.md

@@ -5,82 +5,132 @@
 
 Every entry here is extracted from the comment beside the code that implements it, so this file cannot describe a gesture the application does not have. Add one by writing a `GESTURE:` block next to the implementation; there is nowhere else to write it.
 
-17 gestures, in 2 places.
-29 gestures, in 3 places.
+30 gestures, in 3 places.
 
 ## Develop
+
 ### Set the white balance from the photograph
+
 - **Touch** — Press "pick" in the group's heading, then tap something neutral in the picture
 - **Pointer** — Press "pick", then click something neutral
+
 Sampling a neutral is the first move of the tonal pass — every colour judgement afterwards is measured against where the grey was put — and guessing at two sliders until a wall stops looking green is the wrong way round. One click is one sample and one step to undo; the sliders stay, because a sampled neutral is where the decision starts rather than where it ends.
-<sub>`ui/dr-ui/ui/adjust.slint:157`</sub>
+
+<sub>`ui/dr-ui/ui/adjust.slint:158`</sub>
+
 ### Magnify the photograph by any amount
+
 - **Touch** — Pinch it with two fingers
 - **Pointer** — The scroll wheel over it
+
 Anchored on the fingers' midpoint, and on the pointer, so the gesture reads as magnifying the picture rather than sliding it about. Double-tap is the way to an exact 1:1; this is the way to everything in between.
-<sub>`ui/dr-ui/ui/app.slint:1981`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:1759`</sub>
+
 ### Move a magnified photograph about
+
 - **Touch** — Drag it
 - **Pointer** — Drag it
+
 Only once there is something outside the viewport to reach, which is why the cursor becomes a hand exactly then. The view is clamped to the frame: panning past the edge would show undefined area beside the photograph, and that reads as a rendering fault rather than as the end of the picture.
-<sub>`ui/dr-ui/ui/app.slint:2134`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:1912`</sub>
+
 ### Take back the last change
+
 - **Touch** — Tap the step above the current one in the History list
 - **Pointer** — Click it, or press Undo in the History header
 - **Keyboard** — Ctrl+Z
+
 A whole drag is one step, so undo takes back a decision rather than a frame of a gesture. The list is there because arriving six steps back costs what arriving from one does.
-<sub>`ui/dr-ui/ui/app.slint:2301`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:2079`</sub>
+
 ### Do it again after taking it back
+
 - **Touch** — Tap the step below the current one in the History list
 - **Pointer** — Click it, or press Redo in the History header
 - **Keyboard** — Ctrl+Shift+Z
-<sub>`ui/dr-ui/ui/app.slint:2314`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:2092`</sub>
+
 ### Copy the settings from this photograph
+
 - **Touch** — Press Copy in the Settings panel
 - **Pointer** — Press Copy in the Settings panel
 - **Keyboard** — Ctrl+C
+
 The panel is the copy that has to work: a tablet has no modifier key to hold and no menu bar to hang the action from. The shortcut is an accelerator for a control that is on screen either way.
-<sub>`ui/dr-ui/ui/app.slint:2347`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:2125`</sub>
+
 ### Paste the settings onto this photograph
+
 - **Touch** — Press Paste in the Settings panel
 - **Pointer** — Press Paste in the Settings panel
 - **Keyboard** — Ctrl+V
+
 The button names what would be pasted — "3 adjustments", and whether the crop is coming with it — which the shortcut cannot say. Both paste the same scope.
-<sub>`ui/dr-ui/ui/app.slint:2359`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:2137`</sub>
+
 ### Change which group of adjustments is on screen
+
 - **Touch** — Tap a group in the rail down the left
 - **Pointer** — Click a group in the strip above the develop column
 - **Keyboard** — [ and ] step through them, wrapping round through "everything"
+
 The groups are whatever the operation set declares itself to be about, so there are as many as the pipeline has and no key can be assigned to one of them by name. Stepping is the binding that survives a node being added.
-<sub>`ui/dr-ui/ui/app.slint:2387`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:2165`</sub>
+
 ### Look at the photograph at 1:1
+
 - **Touch** — Double-tap the photograph
 - **Pointer** — Double-click it, or press the zoom readout floating over the canvas
 - **Keyboard** — Z
+
 Noise reduction and capture sharpening are judgements about single pixels, and a fitted view averages several of the file's into each one on screen — so the frame looks softer than it is and the correction goes too far. The point and the magnification survive opening the next photograph, which is what makes checking the same eye across forty portraits forty keystrokes rather than forty pans.
-<sub>`ui/dr-ui/ui/app.slint:2422`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:2200`</sub>
+
 ### Move to the next or previous photograph
+
 - **Touch** — Tap a frame in the roll along the foot of the canvas
 - **Pointer** — Click a frame in the roll
 - **Keyboard** — Right arrow or space for the next, left arrow for the one before
+
 The edit on screen is saved on the way out, so stepping through a folder is as much a departure as going back to the grid and loses nothing.
-<sub>`ui/dr-ui/ui/app.slint:2452`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:2230`</sub>
+
 ### See the photograph before you edited it
+
 - **Touch** — Press and hold "Before"
 - **Pointer** — Press and hold "Before"
 - **Keyboard** — Hold \
+
 Held rather than toggled, and no split screen: a split halves the working image on the tablet the column was sized for, and the comparison photographers describe making is a flick back and forth. It takes no history step, so checking whether a frame is overcooked costs nothing to undo afterwards.
-<sub>`ui/dr-ui/ui/app.slint:2576`</sub>
+
+<sub>`ui/dr-ui/ui/app.slint:2354`</sub>
+
 ### Put one control back to its default
+
 - **Touch** — Double-tap its track
 - **Pointer** — Double-click its track, or right-click it
+
 The column is 280px wide and the colour mixer alone puts thirty-six of these in it, so a reset button per row would be most of the width. Two ways in with a pointer because right-click is the one a hand already reaches for and double-click is the one that needs no second button. A group's own reset is in its heading; this is the single control.
+
 <sub>`ui/dr-ui/ui/controls.slint:294`</sub>
+
 ### Show or hide one mask layer
+
 - **Touch** — Tap the ring at the head of its row
 - **Pointer** — Click the ring at the head of its row
+
 Disabling a layer is the before-and-after a local edit constantly wants, so it is one press away rather than inside the row. It is an edit and does take a history step, unlike holding "Before" — the layer really is off until it is switched back on.
-<sub>`ui/dr-ui/ui/masks.slint:137`</sub>
+
+<sub>`ui/dr-ui/ui/masks.slint:164`</sub>
 
 ## People