DunneFlow · Working with it
Settings
Every setting in the dashboard, what it does, where it is stored, and the settings that live next to what they change.
Open ⚙ Settings in the top bar. Settings are stored in your browser, per program, and stay on your machine.
Appearance#
Theme: Light, System or Dark. System follows your operating system. Both themes are designed, not inverted.
Interface scale: 88%, 100%, 113%, 125% or 150%. One multiplier over type, column widths, row heights, icons and graph nodes.
Colour#
Colour separates meanings in only two places: a difference (what only one version has) and severity in the anomaly worklist. Both use red, so they are set together. Three sets are offered, each with light and dark variants, and each states two measurements:
| Set | Contrast | Separation |
|---|---|---|
| Red and green | 5.34:1 | ΔE 5 |
| Blue and orange | 4.86:1 | ΔE 43 |
| Muted | 4.84:1 | ΔE 10 |
- Contrast says whether a colour can be read (4.5:1 is the minimum for body text).
- Separation says whether two colours can be told apart, taken as the worst of normal vision, deuteranopia and protanopia.
Red and green is the default and the weakest when red and green are hard to tell apart. Blue and orange is built to stay separable. Muted is the default hues at lower chroma, for readers who find it loud; it is quieter, not safer. Where two colours are close, the page says so.
Colour is never the only carrier of meaning: confidence is line style, a boundary kind is an icon plus a label, and severity carries a glyph.
Plate layout#
How a graph plate arranges its contents: By structure (a sunflower spiral, instant and the same every time, so you can remember where things are) or By connection (connected things pull together, which greatly reduces crossings). The page says whether your browser can run the solve on the graphics card. Neither changes what the map says, only where things are drawn, so selection, search and the trail survive the switch.
What opens, and what shows#
| Setting | What it does |
|---|---|
| Startup screen (Cover / Package graph) | Which one you land on. |
| Show the trail | Show the strip recording where you have been. |
| Steps the trail shows (6 / 12 / 25) | How many fit on the bar. Back reaches the full history either way. |
| Cursor over the diagram (Arrow / Crosshair / Hand) | The pointer in Diagram view. |
| Flow arrow thickness (1× to 4×) | How heavily arrows between boxes are drawn. |
| Menu order (Ways in first / Explore first) | Which group comes first in the navigator. |
| Routines listed per package (50 / 100 / 200 / 500 / All) | How many routines each package lists before truncating. |
| Navigator groups (One at a time / All at once) | Whether opening a group closes the others. |
| You are here | The marker over a selected node: shown or off, reticule or not, placement, colour. |
| The graph's ground (Follow the theme / Always dark) | The graph's background. |
| Show edges while moving | Keep links drawn while the camera turns. |
| Graph layout (Stack / Overview) | Two drawings of the same selection. |
| Proportion bars on the cover | Bars beside each count on the cover. |
| Tags on their own line when a name is long | Layout of Where to start. |
| Wrap the evidence line | Wrap or truncate the line under each name on the cover. |
| Ambient anomaly badges | Mark anything carrying a finding wherever it appears. |
| Scroll change bands in place | Whether each band on the change worklist scrolls inside itself. |
| A navigator name too long for its row (As it is / Cut it / Wrap it) | Long-name handling. |
| Fit the toolbar to the window | Keep the one-row toolbar within narrow windows. |
| Version strip on one line | Wrap the strip, or scroll it. |
| Keep the panes inside the window | Panes yield rather than running off. |
| Fold a pane the window cannot fit |
Usage#
A count of which views you actually open, marked local only · never leaves this machine. It exists because several settings offer two options that were genuinely tied, and this is how one of them can eventually be retired on evidence.
Settings that live elsewhere#
These are remembered per program like the rest, but set where you can see their effect:
- Graph spacing, spreads, plate width, node sizing and plate order: the graph's HUD. See Graph.
- Row density: above the routine table.
- Which panes are open, and how wide: the pane rails and drag handles.
- The three comparison overlays: the ◆ changes button in the code browser, above the routine table, and on the anomaly worklist. They are separate because their costs differ: the code overlay makes code harder to read; the routine and table marks are free; the findings overlay is the most expensive to compute, so it is fetched only when you open the worklist. None is shown when there is only one version.
Clearing settings#
There is no reset control. Settings live in your browser's local storage, keyed per program, so to clear them, clear site data for the address the dashboard is served on. Nothing else is lost: the map is on disk and every setting has a default.
Something unclear or out of date? Tell us.