Well, that was my original thought when debugging this code also.
But if there is a run loop nested inside of ours, and someone
calls QuitEventLoop(), why would our event loop handler get the
quit message? Shouldn't the innermost event loop get the quit
message, absorb it, and then our event loop would keep on happily
pulling messages, none the wiser?
Yes, that's what will happen - so if you're getting
eventLoopQuitErr, then someone is calling QuitEventLoop while
immediately inside your runloop invocation. For example,
WakeUpProcess() will call QuitEventLoop.
OK, thanks for the pointer. We can take it from here.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
