Thread-topic: CFRunLoopStop too powerful when invoked by bootstrap per-user daemon?
User-agent: Microsoft-Entourage/11.3.6.070618
Title: CFRunLoopStop too powerful when invoked by bootstrap per-user daemon?CFRunLoopStop is documented as stopping the “innermost activation” of the given run loop. In a regular application (a Cocoa app which calls NSApplicationMain), this seems to be the case. However, in a bootstrap per-user daemon (which calls CFRunLoopRun and CFRunLoopRunInMode), CFRunLoopStop seems to stop all activations of the run loop. Or perhaps I should say both, since we have only two. This happens under both Tiger and Leopard. Has anybody else encountered this? Is there a downside to simply invoking the outer run loop again if/when it exits before we wanted?
— Pete Gontier <http://www.m-audio.com/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
This email sent to email@hidden
