On Wed, May 6, 2009 at 12:58 PM, Eric Hermanson <zmons...@mac.com> wrote: > > On May 6, 2009, at 12:24 AM, Michael Ash wrote: > >> Background threads, whether directly managed by you or >> indirectly created by NSOperationQueue, do not use a runloop by >> default. > > I did not realize that. I knew threads created by the user did not use > NSRunLoop, but I assumed threads created by NSOperationQueue did use > NSRunLoop in some way. So does this essentially mean that you cannot use > the performSelector... functionality from inside an NSOperation main method > because the NSOperationQueue thread that runs the operation does not have a > run loop?
Can you be more specific? There are a *lot* of different performSelector... methods. Most of them have nothing to do with the current runloop and will thus work just fine. The "afterDelay" variants work like a timer and do depend on the current thread running a runloop, and so can't be used in that context unless you're running the runloop manually. Mike _______________________________________________ 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
