Why doesn't autoversion on close just save like the recovery document autosave? Some crashes don't register as crashes and backup save is lost.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I've searched around to see if there was a better way to tweak the autosave feature. I sort of understand why there are the two separate autosave features, but it would make more sense to have the autoversion on close accessable like the recovery documents and without forcing it to be the latest version.
The problem I frequently have is that sometimes my program will freeze (tends to mainly happen in drawing mode), I will leave it for a while to make sure it's frozen for good, then try and click and close until the crash window comes up. Quite regularly, the program is frozen but it doesn't initiate a "crash" alert and so the only way is to close the program from task manager which apparently does not register as a crash. This means that even though everything is being saved every 5 mins, certain crashes will not allow me to open the backups and it is possible to lose hours of work.
What is the point of the autosave crash feature backing up every 5 minutes if they are only accessible with a specific type of crash?
I could use the autoversion on close, but as others have mentioned in other threads, I don't want all the latest versions to automatically be the last iteration of the closed window. If I am saving manually I am 100% I want that to be the latest version, if I don't manually save and I close the program, the autoversion should be there as backup to open up if needed.
So yeah, essentially just an autosave on close (NOT autoversion on close), stored and accessed exactly like the recovery documents, but generated on close (or literally generated any time, I just want to be able to access this as needed instead of only being able to see crash recovery documents from months ago).
