Re: NSRunloop performSelector needs CFRunLoopWakeUp ?
Re: NSRunloop performSelector needs CFRunLoopWakeUp ?
- Subject: Re: NSRunloop performSelector needs CFRunLoopWakeUp ?
- From: "Adam R. Maxwell" <email@hidden>
- Date: Sat, 24 Jan 2009 20:07:28 -0800
On Jan 24, 2009, at 10:18 PM, Michael Ash wrote:
On Sat, Jan 24, 2009 at 3:42 PM, David Hoerl <email@hidden> wrote:
[...]
The current app is single threaded.
Can anyone shed any light on why the CFRunLoopWakeUp() call is
necessary? Is
there some other issue I'm missing?
Look at the big master list of what Cocoa classes are thread safe:
The OP wrote that his app is single threaded, so the lack of NSRunLoop
thread safety shouldn't be a problem. It sounds like the event loop
is blocking the runloop, so maybe posting a custom event would work as
well as tickling the runloop...but that's just a guess.
--
Adam
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden