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
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
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
Although it's not mentioned in the 10.7 AppKit Release Notes, the various
methods involving document saving are invoked sequentially in 10.7, rather than
nested as they have always been, even if you have *not* enabled the new
asynchronous document saving feature.
In the following lines, logs
Here's a more readable version of my previous message. (Forgot that email
clients think lines beginning with are quoted.)
Although it's not mentioned in the 10.7 AppKit Release Notes, the various
methods involving document saving are invoked sequentially in 10.7, rather than
nested as they
On 17 Aug 2011, at 23:18, Jerry Krinock wrote:
Although it's not mentioned in the 10.7 AppKit Release Notes, the various
methods involving document saving are invoked sequentially in 10.7, rather
than nested as they have always been, even if you have *not* enabled the new
asynchronous
