Re: Temporarily disabling autosave
Re: Temporarily disabling autosave
- Subject: Re: Temporarily disabling autosave
- From: Quincey Morris <email@hidden>
- Date: Thu, 25 Apr 2013 10:05:13 -0700
- Sun-java-system-smtp-warning: Lines longer than SMTP allows found and truncated.
On Apr 25, 2013, at 09:10 , Steve Mills <email@hidden> wrote:
> Saving in place is not something most users expect, because it hasn't been done that way on all the common platforms.
Uh, you can't make statements like that without citing evidence. Have you surveyed most users on this point? There are plenty of users to whom the idea of saving is itself unexpected -- because the [pre-Lion] need to save changes implied that your computer was otherwise going to discard your changes, and why would it do that???? For people with this mindset, needing to save explicitly is like some kind of punishment.
> 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).
Autosave-in-place was explicitly designed to avoid the problem you're complaining about!
Remember, way back in this discussion, I said that the post-Lion saving behavior made sense only in its own terms, not in terms of the pre-Lion behavior. It sounds like your approach to this is stuck in pre-Lion terms, and so of course the new behavior seems wrong to you.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden