autosave files do not save the entire document but rather incremental snippets only that can't be used without the "really" saved document file. autosave files is that they don't help at all if app-internal issues occur. It needs to be stressed that it is not an autosave function. autosave feature would work more reliable – and never would lose their contact to the savedversion of the document. – Whereas it also happens that it requires several trails to open a saved document (same set of error messages). Ironically, for the majority of this error situations caused by "Save" an immediate second or third trial is well able to open the file, often, not always, including the recent changes, and at least in the last saved state of the document. From this perspective the concept for autosave in Affinity is fine.īut I am rather concerned when a simple, usual Save action suddenly appears to trigger one of the various "can't read" … "access lost" … "must be closed" … "file corrupted" error messages (while working in that file did not). Usually I am glad when the app reopens / restores a current document after an app crash which usually contains the most work since my last save. (.) I'd like to support the call for an autosave proper, like most other software. Unfortunate crashes where the restore file is corrupted and no file can be restored.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |