On Oct 30, 2007, at 5:11 PM, Jesper Storm Bache wrote:
Does this mean that my AppleEvent specifications and my Carbon
events (that go to the application event target) now need to be
unique?
I.e. I cannot have a Carbon Event called 'MyEv' and an AppleEvent
called 'MyEv' without the risk of confusing these when I receive an
event on the Application event target?
Yes, that is correct. So far, we haven't seen any cases where
applications use the same codes for a Carbon event and an AppleEvent.
The document also lists:
"...The AppleEvent handlers will not be called until your Carbon
event handler returns"
I assume that if I return noErr, then the AppleEvent handlers will
not be called at all?
That's correct. Returning noErr says "I'm done handling the event",
and AppleEvent handlers aren't called at all.
-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
