Re: Very different Document Saving in Lion, even without enabling asynchronous
Re: Very different Document Saving in Lion, even without enabling asynchronous
- Subject: Re: Very different Document Saving in Lion, even without enabling asynchronous
- From: Mike Abdullah <email@hidden>
- Date: Sun, 21 Aug 2011 10:00:11 +0200
I was talking about the -saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo: method that -saveDocument: has always been documented to call. In practice that method operated synchronously unless there was an error, but it's clearly an asynchronous API
Sent from my iPad
On 21 Aug 2011, at 06:46 AM, Jerry Krinock <email@hidden> wrote:
>
> On 2011 Aug 17, at 16:30, Mike Abdullah wrote:
>
>> Seeing as you knew it called an asynchronous method internally, you must have known that it might potentially return before saving is finished.
>
> Thank you, Mike. I'm not surprised to see the new behavior after enabling asynchronous saving. The surprise is the new behavior *without* enabling synchronous saving (it should still be "synchronous"), and the fact that it is now it behaves completely different from what is shown in the documentation, and there is no mention of this change in the Release Notes.
>
> _______________________________________________
>
> 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
_______________________________________________
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