Chris Idou ([EMAIL PROTECTED]) on 2008-12-03 11:00 PM said: >> how will you eventually make it shut down even if you do >> do that, or will it just hang out there until the application >> terminates? > >Good question. I had assumed that something like >[myThread performSelector:@selector(exit) onThread:myThread ... > >would do the trick. Would this be a "nice" way to do it?
Well, the docs for exit say "Invoking this method should be avoided as it does not give your thread a chance to clean up any resources it allocated during its execution". You said you wanted your thread to 'patiently wait for performSelector:onThread: calls'? When do you want it to stop waiting? If at app quit time, then just leave it around. If earlier, then just send it a message to clean itself up (dealloc memory, etc.) and invalidate the timer. Then you are back to having no runloop sources and voila. Sean _______________________________________________ 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]
