Re: -mouseMoved: not being called
Re: -mouseMoved: not being called
- Subject: Re: -mouseMoved: not being called
- From: Ron Fleckner <email@hidden>
- Date: Mon, 21 May 2007 09:40:11 +1000
On 20/05/2007, at 5:29 PM, Giovanni Donelli wrote:
I believe mouseMoved events are sent only to the foremost/key window.
once possible explanation is that your user has something that
prevents the window from being in the frontmost,
I would try to override mouseEnter to force the window to be front and
key and see how it goes, this might be helpful to understand what is
not working.
Giovanni
On 5/20/07, Ron Fleckner <email@hidden> wrote:
Hi,
One user of my app reports that a feature which relies on getting -
mouseMoved: events isn't working.
What could be a possible cause of this?
Ron
Giovanni, you could be onto something here. The window in question
is a subclass of NSWindow with NSBorderlessWindowMask. I've
overridden accept, become, resign and isFirstResponder to make it a
part of the responder chain, as well as canBecomeKeyWindow which
returns YES. To check the window's status as key, I've made it it's
own delegate and have implemented - (void)windowDidBecomeKey:
(NSNotification *)aNotification, but the notification is never sent,
or at least never received.
However, this still leaves the question as to why the mouseMoved:
events work on my two computers, but not on some others. At least
one of the machines here doesn't have DevTools, so it's not an issue
of it working only on the dev machine.
At the moment, the frontmost/key issue seems to be the most likely
cause. Thanks for the thought, I'll keep looking into it.
Ron
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden