Returns a Boolean value indicating whether it is probably safe to autosave document changes.
- macOS 10.7+
falseis returned, a pointer to an error object that encapsulates the reason the document should not be autosaved.
true if autosaving the document is probably safe; otherwise,
The default implementation of this method checks for documents that have not been changed in a while ("a while" is subject to change) or are saved in folders where the user typically does not edit documents (the
~/Downloads folder, for example). When it senses one of those cases it returns
false with an
NSError object that has recovery options like Duplicate, Cancel, and Unlock.
In an app that has adopted autosaving in place by overriding
autosaves to return
true, you can override this method to customize the autosaving safety checking that
NSDocument does by default. You can remove the
NSDocument default checking by overriding this method and not invoking super. You can add to the
NSDocument default checking by invoking super and then doing your own checking if
[super check did not signal an error. For example, TextEdit overrides this method to ask the user what to do when opening a document file has been lossy and overwriting that file might therefore be lossy.
When autosaving in place is turned on an
NSDocument object may invoke this method when it receives notification from its
NSUndo object that the user changed the document, or undid or redid a change. If an error is returned,
NSDocument presents the error to the user, allowing the user to choose a recovery option. If the user chooses a recovery option, then
NSDocument invokes this method again until no error is signaled, to make sure that all checks have been done. This means that when you signal an error and the user’s choice of recovery option indicates that they have seen and disregarded a safety concern, you must record that fact and not do that particular safety check again. Once all errors are handled,
NSDocument continues by invoking
update. If the user does not recover from an error, then
NSDocument invokes one of the
redo() to roll back the change. So, some of the
NSError recovery options the user can choose, like the
NSDocument options Duplicate and Cancel, should indicate failed recovery and cause the document to remain unchanged afterward.