Am 01.05.2008 um 16:18 schrieb Michael Vannorsdel <[EMAIL PROTECTED]>:
I read over the docs for this function and not coming to the same
conclusions. Being an async function it should be implied the
callback will be used if the starting function succeeded.
The operative word being "should". Not everything that should be is.
This is the
whole point of async operations and the only way to get status reports
from them besides having to poll, which defeats the purpose of async
operations. Also, the minimum time argument as the docs explains is
there to limit the time between multiple calls for a "single
stage" (ie kFSOperationStageRunning) for flood prevention and doesn't
apply to stage changes. Also, the presence of a
"kFSOperationStageComplete: The file operation is complete." makes it
pretty clear there should be a status report upon completion.
The only error here I believe, as explained by someone else, is
forgetting to schedule the event source with the runloop for
processing. However after reading the docs I too am lead to believe
(and know from experience with this function) that the callback is
used and is called upon completion.
Rereading all of the documentation (not just that for the
FSCopyObjectASync function) I have to agree with your analysis. It's
interesting though that the OP reported that the copy operation
itself worked fine, apparently without any runloop support.
Thanks for making sense of the sparse documentation ;-)
Mike
--
Mike Fischer Softwareentwicklung, EDV-Beratung
Schulung, Vertrieb
Note: I read this list in digest mode!
Send me a private copy for faster responses.
_______________________________________________
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 [EMAIL PROTECTED]
