Re: autosavesInPlace and sandbox
Re: autosavesInPlace and sandbox
- Subject: Re: autosavesInPlace and sandbox
- From: Kyle Sluder <email@hidden>
- Date: Fri, 07 Sep 2012 08:01:16 -0700
On Sep 7, 2012, at 7:45 AM, Markus Spoettl <email@hidden> wrote:
> On 9/7/12 3:36 PM, Mike Abdullah wrote:
>>> you are not asked if you want to keep it
>>
>> So here's the real problem it seems; you run into customers accidentally
>> modifying documents. Normally they would be warned as they quit or close the
>> doc, but with autosave-in-place, that doesn't happen.
>>
>> Some good news in 10.8: users can turn on a system preference so that they
>> get effectively get back the warning behaviour. Closing a document will warn
>> you if there are "unsaved" changes. However, the file on disk will already
>> have been updated. That might bother them; I don't know.
>>
>> But more importantly, isn't this exactly what 10.7's concept of locked
>> documents tried to solve? If the doc hadn't been edited in a while, it would
>> be marked as locked. So the first time any edit occurred, a sheet popped down
>> asking if the user wanted to go ahead with the edit, duplicate the doc or
>> cancel.
>>
>> Was that not kicking in for your typical customers? Perhaps because the
>> document was too recently edited? 10.8 does throw this out of the window. But
>> what you could do is override -checkAutosavingSafetyAndReturnError: so that
>> it always returns NO when a doc is first opened. If your app is primarily
>> used as a viewer, that could be a neat way for you to always ask if the first
>> edit is intended.
>
> Wow, and all that for preventing the stupid thing from saving, something that was so easy up until 10.7. The whole know it all attitude NSDocument has been taking lately is highly annoying. The fact that some knowledgeable people here (like yourself and Kyle) seem to indicate that there soon will be no way to opt out of it (at an API level) is highly frightening.
I must stress that this is nothing more than an educated guess on my part. But if people find Lion Autosave confusing enough by itself, do you think Apple really wants two saving paradigms forever?
--Kyle Sluder
_______________________________________________
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