Settings
Three cards, and every control in them is wired to something. Anything that could not be honestly implemented for V1 was removed rather than left inert.
Appearance
Three themes, and the choice is explicit:
- Local Dark — the default. Dark navy surfaces with a cyan accent; the look the application is designed around.
- Dark — conventional neutral dark, with no brand hue in the surfaces.
- Light — built as a light interface rather than an inverted dark one: a cool near-white canvas with white cards above it.
Monitoring
The refresh interval selects how often the sampler produces a snapshot: 500, 1000, 2000 or 5000 milliseconds. The default is 1000.
The sampler owns this cadence. The interface never triggers a scan itself, so nothing you do in the window — sorting, filtering, switching mode, opening a panel — causes extra work.
A longer interval costs less and makes rate-derived values smoother; a shorter one reacts faster to a service starting or stopping. The cost of the last tick is shown live in the Overview meta row, so the trade-off is measurable rather than guessed.
About
Reports the running version, the licence, the publisher and the application identifier (com.silentminds.localdocks). The version is read from the application at runtime rather than hard-coded into the interface, so it cannot drift from the installer and the executable metadata.
The card also carries a standing note that LocalDocks is running without elevation and never requests administrator rights.
Options that deliberately do not exist
| Not present | Why |
|---|---|
| Confirm before terminating | A safety confirmation you can switch off is not a safety confirmation. It is always on. See Processes. |
| Row density, loopback filtering, system-port visibility, browser choice | Each depends on backend behaviour that does not exist yet. A toggle that does nothing is worse than an absent one. |
| Telemetry and crash reporting | There is nothing to switch off. LocalDocks has no network client, no analytics and no crash reporter. |
Where settings are stored
Theme, interval and mode are kept in the application’s own local storage inside your user profile. They survive a restart and an upgrade, and they never leave the machine.