Appearance
Command-line options
DigitalWorksBench.exe [options] [circuit-file]
--data-dir <dir> Keep settings, auto-save, themes and the error log in <dir>
(default %LOCALAPPDATA%\DigitalWorksBench; also the DWB_DATA_DIR env var)
--config <file.json> Apply settings from a JSON file (same keys as settings.json; a subset is fine,
comments and trailing commas allowed)
--theme <name> light | dark | system
--set <key=value> Override one setting, e.g. --set gridStyle=Lines (repeatable)
--open <file> Open a circuit at startup (a bare path does the same)
--no-recovery Do not offer to recover an auto-saved circuit
-h, --help Show this help- Precedence, lowest to highest: saved settings,
--config,--theme,--set. - Keys are the camelCase names in
settings.json(theme,gridStyle,gridOpacity,showGrid, ...). Valuestrue,falseand numbers are typed; anything else is a string. Unknown keys and values of the wrong type are logged and skipped; the rest still apply. - Overrides are in memory. If you save preferences while running, the merged values are written to
settings.json, so use--data-dirto keep test runs away from your real settings. --open(or a bare path) skips the recovery prompt, since a file was asked for explicitly.- Invalid arguments (unknown option, missing value, bad theme, two files) are written to
errors.logas[startup]entries and the process exits with code2without opening a window.
Testing
tests/DigitalWorksBench.E2E launches the app with --data-dir <temp> --no-recovery and can add its own arguments per test class (override AppArgs), for example --open <sample.dwcircuit> or --config <file>.
Sample configs
docs/configs/light.json and docs/configs/dark.json switch the app chrome, canvas colours and part editor together:
DigitalWorksBench.exe --config docs\configs\light.json --data-dir %TEMP%\dwb-light
DigitalWorksBench.exe --config docs\configs\dark.json --data-dir %TEMP%\dwb-dark