On Mar 5, 2009, at 2:45 PM, Ken Thomases wrote:
Yeah. You can provide feedback for the documentation to ask for clarification.
Done. :-)
So, it's not even sufficient that the launch thread continues to exist, it must run its run loop.
Good point.
By the way, you don't necessarily need to use a condition lock to learn when the task has been launched. If you have the secondary thread tell the main thread to launch the task using - performSelectorOnMainThread:withObject:waitUntilDone: and pass YES for the wait parameter, you get that synchronization pretty simply.
Yes, you're right. Though since I've been bitten by the waitUntilDone:YES behavior before (entirely my fault), I was trying to think of a new way to avoid it and still achieve a similar result.
Alrighty, thanks Ken. Just looking to see that I had my head on straight. Looks like I did. :)
Cheerio, -- Seth Willits _______________________________________________ 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
