At present, if one designer/annotator opens another designers file to look around/copy something, and inadvertently changes something, there is no way to exit the file, without that change being automatically saved.
The only way to be sure is to get in the habit of continual undo’s to get back to the point entered.
It would be extremely beneficial to have a setting to allow versions to only be saved via an ‘explicit save’, rather than the current implied one (when anyone exits a file).
This would allow larger teams a means to insulate themselves from files easily getting messed up.
Hey Jorge, thanks for sharing the possible workaround. That seems quite an involved solution to go through to deal with a situation that we see happening a lot, but it also assumes that someone has realised quite quickly that changes have been made. Often it’s days and/or multiple edits later that we realise that things have been unintentionally moved or removed from the file. Reverting to previous versions is even tougher then.
If it’s unfeasible to add a setting, then another solution could be to have an “Exit Without Saving” command in the menu.
Well, I guess the main issue here is when collaborating. If more than one editor modifies the document, is not always possible to quit without saving since two or more edits may be concatenated.
@leohans is right, this scenario would make it impossible to close the file without saving the changes.
Maybe there is a way to select a file to be opened as a disconnected copy (or a branch like in git).
