Re: Cocoa-dev Digest, Vol 3, Issue 406
Re: Cocoa-dev Digest, Vol 3, Issue 406
- Subject: Re: Cocoa-dev Digest, Vol 3, Issue 406
- From: "Tom Harrington" <email@hidden>
- Date: Thu, 30 Mar 2006 15:12:48 -0700
On 3/30/06, Raleigh Ledet <email@hidden> wrote:
> If you need a Cocoa equivalent of the Carbon EventMonitorTarget
> please file a bug for it.
I'm not too concerned about needing to drop a few Carbon calls into my
code, if I can make it work, but I'll do this anyway because it'd be a
nice improvement. I may file a bug related to the keyboard events not
getting posted normally, though (unless someone has an explanation of
why the behavior could be considered normal).
> Monitor Targeted events only occur when you app is not the
> foreground. When you app is in the foreground the events come in the
> normal way.
>
> I have a similar problem with tablet proximity events. I register for
> the Carbon Event I'm interested in on the MonitorTarget, however, the
> event never comes through my installed Carbon Handler. Instead the
> event comes through the normal Cocoa event chain. The same is
> probably happening for your events as well. Since you app is in the
> background, I don't know which view would get the event. It may
> behoove you to override NSApp's sendEvent: to catch the event there.
> Then reroute or broadcast a notification about the event to the rest
> of your app.
That's it! If I implement sendEvent: in my NSApplication subclass,
the Carbon events I've signed up for show up there. Thanks, it hadn't
occurred to me that I'd be getting them this way.
--
Tom Harrington
email@hidden
AIM: atomicbird1
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden