On Sep 29, 2011, at 4:41 PM, Kyle Sluder wrote: > [...snip...] > > A general issue I have with asynchronous saving: what if the save > operation fails? The user has now made additional changes, but their > "Save a Version" operation did not create a version for them. So now > they can't roll back to the timepoint they thought they created.
That is true. Perhaps this is something that could be improved in the future. I suppose one way to fix this would be to retain the 'snapshot' used for async saving and retry again later? > Of course I have another question. > > On Thu, Sep 29, 2011 at 12:33 PM, Kevin Perry <kpe...@apple.com> wrote: >> NSDocument's NSFilePresenter methods use >> performAsynchronousFileAccessUsingBlock: internally, so if something else >> current has file access, the NSFileCoordinator requests are indeed blocked >> (or "enqueued"). > > What about NSFilePresenter methods that require presenting a sheet? Do > they instead wrap their calls to -performAsynchronousFileAccess: in a > call to -performActivityWithSynchronousWaiting:NO? Yes. -KP_______________________________________________ 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
