mirror of
https://github.com/utmapp/UTM.git
synced 2026-10-12 02:24:01 +00:00
osy
cb9e95af4d
Snapshots could only be managed through scripting. Split the details view into tabs (a tab view on macOS and a segmented control elsewhere, following the HIG) and add a Snapshots tab next to the existing details. The tab lists the current state followed by every snapshot, newest first, along a timeline. A snapshot never changes unless it is overwritten, and restoring one replaces the current state with a copy, so the actions say as much: the current state can be saved as a new snapshot or overwrite the one it is based on, and a snapshot can be restored or deleted. Anything that loses data asks first. A snapshot is based on whatever the current state was based on when it was created. One that follows what it is based on is joined to it so a lineage without branches reads as a single line. A base that is elsewhere in the list is named by a link instead, which keeps branches of any depth from widening the list. The lineage of the focused row is highlighted and only that row shows its actions. Rows choose their layout from the measured width because a regular size class can still be narrow next to the sidebar. The operations only modify an in-memory list for now and no snapshots are read from the VM yet. Whether a snapshot holds the running machine decides whether restoring it resumes the guest or starts it up, so the mark on the timeline is filled for one that does and hollow for one that holds only the disks. Assisted-by: Claude:claude-fable-5-1