On Apr 25, 2013, at 10:21 , Kevin Perry <kpe...@apple.com> wrote: > Actually no—autosaving-in-place means exactly that changes are always saved > to the main document file, hence "in place". There is only ever a single file > per document, even when quitting.
Oops, I obviously got too focused on the "autosave elsewhere" part of this. However, I think the essence of my point was correct. Without activating the options added in Mountain Lion, if you quit with a dirty document and relaunch, it comes back as a dirty document. You've neither lost nor gained anything by quitting. In fact, IIUC, even if you don't quit, a timed autosave will also save the document in place, right? You can still discard your changes, if you wish, which seems to be one of the worries Steve had. Steve also seems worried that autosaved changes are visible to other apps using the same document, but that's a design choice of the post-Lion document architecture, with the whole coordinator/presenter mechanism to support it. Steve might validly be worried about the privacy implications of this behavior, but it seems over-alarmist to call it dangerous or dumbed-down. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
