On Fri, 9 Mar 2007 18:32:30, "Matthew Douglass" <email@hidden>
wrote:
>> Unless mouse moved events are sent with kEventTargetSendToAllHandlers
>> option (which I believe is not the case, otherwise it would be mentioned
>> in the CarbonEvents.h), the mouse moved handler installed on a particular
>> window might interrupt the event flow by means of returning noErr from
>> the handler. Won't that be a problem? I haven't tried using event
> dispatcher
>> target in this context but maybe it's more appropriate.
>
> Well I did try this approach out and it seems to work correctly (so far).
> Is the noErr return value you mentioned only from other windows in my
> application or would it be possible for a non-foreground application's
> window that is behind my app to do this?
Only your app (including "plugins" if any).
> If it's only my application's windows then it is a non-issue (for me) since
> my app only has one window.
Yes. Until three months later you add another window. And two months
after that another programmer of your team (or you) add a mousemoved
handler on that window that will return noErr. Just be careful :)
Event dispatcher target kinda guards you from these potential issues
in this case.
Mike
[Available for hire. Resume on request.]
_______________________________________________
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
This email sent to email@hidden
