dtourolleandClaude Opus 5
65e6a96a65
Every background job reported into a window property of its own — library-thumbs-done, library-pin-total, library-syncing — which only the grid ever read. A pin download that outlived the view it was started from drew nothing at all once the user opened an image, and there was no answer anywhere to "what is this busy with", because the answer was spread across eight properties nothing collected. They report to one register now (ui/dr-ui/src/activity.rs). It publishes an aggregate, which draws a three-pixel bar across the top of the shell in every view, and a row per job, which the settings page lists: scans, thumbnail batches, pin and open downloads, sidecar uploads, the sync and the trash. Failures stay on the list until they are cleared; routine successes do not, or a scroll would bury them. The handle removes a still-running job when it drops, so a worker that dies mid-transfer takes its row with it rather than leaving the bar sweeping for the rest of the session. Also carries in-flight work from a parallel session — the drawn icon set and the dr-pipeline ops split. dr-pipeline's build script does not compile at this commit; ui/dr-ui does, with clippy clean and its tests passing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
15 lines
527 B
YAML
15 lines
527 B
YAML
id: colour_mixer
|
|
order: 100
|
|
rust: ColourMixer
|
|
|
|
why_rust: |
|
|
Thirty-six parameters — twelve hue bands times hue, saturation and
|
|
luminance — generated as a grid, each carrying a `Facet` naming its band and
|
|
the band's centre on the hue wheel. Spelling that out as thirty-six YAML
|
|
entries would be a worse description than the loop that produces it, and the
|
|
band centres are computed rather than listed.
|
|
|
|
placement: |
|
|
Last. It is the finishing control, and it should act on the tones the user
|
|
has already settled.
|