Fix annoying autosave

opened 1 year ago by simon

Autosave is useful. But: it is currently NOT a backup. Let's look at this scenario:

- open model, start editing (autosave every so many seconds)
- tool crashes for some reason
- open model to see what was saved and what was not
- autosaved model is overwritten after autosave interval

Potentially, what could be done is, when a model is opened, and the autosave is newer than the current model, a pop-up window asks the user whether to restore the autosave or load the older model.
This is probably not what we want. The interval is now reduced to 30 seconds (instead of 300) to make autosaves more frequent. A user then just has to make sure to open the autosaved model. A way of doing this cleanly would be to detect a 'proper shutdown' of AToMPM and delete the autosave. Then when an autosave is present, we know AToMPM crashed.

No files, tests, or entry points are named. Start by locating the 30-second autosave logic and the application shutdown handling, then trace how models are opened and autosaves are written. Done requires a decided recovery behavior that preserves an autosave after a crash without overwriting it on reopening.

Written by the indexing model from the issue text.