Open RetroEdit opened 1 month ago
Current behavior will mercilessly overwrite if you made changes you don't want to keep, accomplishing the opposite of the intended purpose.
The intended purpose is mainly to prevent you from losing progress in case something bad happens, like bizhawk crashing (this used to be more common in the past), your PC crashing, power loss etc.
Saving as a (singular) backup file is probably more ideal to allow reverting unwanted changes though and gives more safety in the case that something crashes during the saving action.
This probably isn't a new issue.
Autosave
is on by default and it will overwrite your tasproj without asking.To me, it's clearly wrong to overwrite the current tasproj by default. All other applications that I'm aware of save to a secondary file that can be used as the restore point if you forget to save. It barely has to change the workflow. If the user manually saves, the secondary file can be deleted. If there's a secondary file upon load the program can prompt something like "An autosaved backup file for the current project was found. Would you like to restore it?"
Current behavior will mercilessly overwrite if you made changes you don't want to keep, accomplishing the opposite of the intended purpose.
(Personally, I have grown accustomed to just disabling Autosave upon first launch because autosave used to be a major interruption. It still can interrupt flow, and I prefer to choose when I have it saved.)
Host Env.
I had this occur just now in ed676cda391d25bdb1728ada13b7df21c0a974df
Also confirmed this behavior in 2.9.1