Workspaces¶
A workspace saves a whole setup in one file, so it can be opened again with one click and shared with others: the connections and, for each of them,
- the interface, channel and bus settings, or the log file and speed of a replay,
- whether it was connected (it connects again when the workspace is opened),
- the signal database and its bus, and a CANdelaStudio diagnostic description,
- the display filter and the plotted signals,
- the simulation scripts and panels, and whether the simulation was running,
- the test scripts,
- and which connection was selected.
Saving and opening¶
| Command | Shortcut | |
|---|---|---|
| ⋮ → Save Workspace | Ctrl+S | Saves to the current workspace file, or asks for one |
| ⋮ → Save Workspace As… | Ctrl+Shift+S | Saves to another file (.cxw) |
| ⋮ → Open Workspace… | Ctrl+Shift+O | Opens a workspace; also on the welcome page |
| ⋮ → Recent Workspaces | Reopens a recent workspace; also listed on the welcome page |
Opening a workspace closes the open connections and replaces them with those of the workspace, after asking. The window title shows the name of the workspace.
Sharing¶
Files are stored relative to the workspace file, so keep the workspace together with its databases, scripts and log files, e.g. in a project directory or repository:
bench/
├── bench.cxw
├── vehicle.dbc
├── engine_simulation.py
├── engine_panel.qml
└── vehicle_tests.py
When a file is missing, the workspace opens anyway and the notifications list what could not be restored.
The workspace is a JSON file and can be read or generated by other tools; its format is versioned
("format": "canexplorer-workspace", "version": 1).