My app still has an old world event model of get mouse down then
dispatch it to the window and then onward... I added the app mouse
handler so I could also get mouse wheel events...
Of course this isn't ideal, but since it is a legacy WNE app it was much
less work to do it this way and then simply plug into my prior event
dispatching, etc...
Ando
Why do you need a mouse event handler at the application level? A
situation
like this, where you have something most applications don't need and
which
needs to be special-cased like this every time you find a new scenario
in
which it breaks something suggest thats perhaps a different approach
might
be cleaner and more suitable.
Larry
>
> Thx,
> Ando
>
>
>
> On Jan 19, 2006, at 3:55 PM, Ando Sonenblick wrote:
>
>> Well, my main app window I believe does have some handlers
>> installed on
>> it. But those shouldn't interefere with a separate alert window,
>> right?
>
> No, they shouldn't, but it might be worth setting a breakpoint on
> them and testing to make sure.
>
>> And if it does, I need them so any workaround suggestions?
>
> We'd need to know more about what these handlers do. But as you say,
> if they're just installed on the window (not the application), they
> shouldn't be affecting anything.
>
> -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
This email sent to email@hidden
