I had a problem with this as well. I had not enabled asynchronous saving, but I was reading the document metadata after a saveDocument: call (not even an overridden method, mind you, but just in the same event cycle on the main thread); and this was causing infinite recursion.
I fixed it by using saveToURL:ofType:forSaveOperation:completionHandler: instead of saveDocument:, and put the metadata reading calls into the completion handler. On 2011-08-21, at 12:46 AM, Jerry Krinock 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 (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: > http://lists.apple.com/mailman/options/cocoa-dev/dave.fernandes%40utoronto.ca > > This email sent to dave.fernan...@utoronto.ca _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
