On Jun 30, 2006, at 1:21 PM, Tomas Zahradnicky wrote:
Dear Carbon Developers,
I've found a strange behavior in my app and it seems to be caused
by Navigation Services.
My app's using a custom run loop with ReceiveNextEvent and receives
eventLoopQuitErr message when the put file Navigation Services
dialog gets dismissed.
#0 0x93252e50 in QuitEventLoop ()
#1 0x9316b730 in __NavDialog::TerminateWithUserAction ()
Is this a bug in Navigation services that it allows its own quit to
propagate? The put file navigation dialog is shown with a
NavDialogRun call.
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.
-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
