On Apr 25, 2013, at 10:05 AM, Quincey Morris <quinceymor...@rivergatesoftware.com> wrote:
>> I can't begin to count the number of times I've opened documents, edited >> them in some way, not intending to save those changes. Maybe I just needed >> to, say, find an image in a particular layer of some image editing app, so I >> hid some layers. That sort of thing. But doing something as simple as >> quitting means those changes will automatically change my actual document >> file without even asking if I want to discard them. That's just dangerous. > > You have this exactly backwards. Autosaving-in-place never changes the > *saved* document file. It writes the autosaved document elsewhere. When you > quit with an open, dirty document, there are two copies until you relaunch. > At that point, your document is *still* dirty, and you can *still* close the > document window explicitly, and you get a dialog asking if you want to save > or discard changes (back to the point of the original save, which was before > you quit and relaunched). 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. However, in Mountain Lion, we added preferences that allow you to (1) force documents to close on Quit, and (2) ask if the user wants to keep changes that they haven't explicitly saved (Cmd-S). In the above scenario, when these preferences are enabled, you will be given the option to discard all the experimental / temporary changes (made possible by Versions). -KP _______________________________________________ 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
