How a save becomes a version
Each save creates the next version, numbered from 1 upwards, and the canvas records which version is current. When a save lands, the thread rail beside the canvas confirms it with a line naming the new version, the time, and how many frames and notes the canvas now holds. You never choose how a save is stored. Cortex writes a complete snapshot of the canvas at intervals on its own, so the history stays quick to replay however many small edits sit between snapshots. Saving is protected against two windows fighting over the same canvas. If a second window saves starting from a version that is no longer current, that save is refused withThis canvas was saved from another tab. Reload and try again. Reload the canvas and redo the change. See conflict.
Open the Versions rail
The editor header carries a Versions button with the number of saved versions on it. Opening it shows the rail:- Versions newest first, grouped by day under headings such as TODAY and YESTERDAY.
- Each row names the version, who saved it, and the time.
- The current version carries a CURRENT chip.
- The version you are reading carries a VIEWING chip.
View an older version
1
Open Versions in the editor header
The rail opens beside the canvas.
2
Select the version you want to read
The header pill switches to a read-only viewing state, for example Viewing v4 · read-only, and a banner across the canvas repeats the version and when it was saved.
3
Return to the current version
Choose the control that names the current version, for example Back to v7.
Restore an older version
Restoring does not rewind the canvas and does not throw away the work you did since. It takes the older version and saves it again as a brand new version at the top of the list.1
Select the older version in the rail
Its row is highlighted and the canvas shows it read-only.
2
Choose the restore control
It names the version you picked, for example Restore v4.
3
Carry on from the new version
The restored content becomes the newest version and the current one. Its row is labelled as restored from the version it came from.
Nothing is deleted by a restore. The version you were on before stays in the list, in its place, and you can restore that one in turn if you change your mind.
Compare with the current version
Beside each older version the rail offers a compare control, which names the current version, for example Compare with v7, and sets that version against the one you are working on. What the comparison itself draws is not documented, so expect the control before you expect a particular view.What versions do not do
- A single version cannot be removed from the list on its own. The list only grows, including when you restore.
- There is no clock running against your history. As long as you keep the canvas, its earlier versions stay with it.
- Versions belong to one canvas. They are not shared between canvases, and a library item has no version list of its own.
Deleting a design hides it rather than erasing it. Its versions and images stay with it and it can come back, and the Design desktop app offers an undo for ten seconds immediately after the delete. See Design canvases.
Related
- Generate and edit - where saves happen and where the Versions button lives.
- Design canvases - what a canvas is, and what deleting one does.
- Export a design - take a version out as a file.
- Design troubleshooting - a save that was refused, or a canvas that will not open.