On Jun 30, 2006, at 3:20 PM, Tomas Zahradnicky wrote:
I don't really think this is a bug. eventLoopQuitErr is the
correct result to be returned from ReceiveNextEvent when someone
calls QuitEventLoop. You can't really depend on the result of
ReceiveNextEvent being deterministic because you have no guarantee
that parts of the toolbar won't call QuitEventLoop for their own
reasons.
I'm not using any toolbars
Whoops, I meant "toolbox", not "toolbar".
but have to use RNE because I could not use nested
RunAppModalLoopForWindow. IIRC one QuitEventLoop quitted all nested
RunAppModalLoopForWindows so I had to choose a different option.
Hmm, I wouldn't expect that to be a problem, actually. We should
reset that state after the current event loop has returned.
In any case, I think the proper approach is generally just to ignore
a return value of eventLoopQuitErr from ReceiveNextEvent, and loop
around to call ReceiveNextEvent again.
-eric
_______________________________________________
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
