Along with threads and various asynchronous techniques already
mentioned, you should also consider creating a separate UI-less
"foundation tool" to perform your lengthy task, controlled with NSTask
in your main app. This yields all of the benefits of a thread, with
none of the threading pitfalls. Getting real-time feedback (for a
progress indicator, for example) from the task is more complex than
with a thread, and getting result data back is slightly more involved,
but the absolute freedom from threading issues is often worth it.
Several of Apple's utility apps are constructed as a UI shell that
invokes one or more tools.
_______________________________________________
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
