Re: Observing contextual menu openings
Re: Observing contextual menu openings
- Subject: Re: Observing contextual menu openings
- From: Eric Schlegel <email@hidden>
- Date: Wed, 03 Apr 2013 08:43:14 -0700
On Apr 2, 2013, at 2:24 PM, Patrick Cusack < email@hidden> wrote: I am observing my application process looking for an kAXMenuOpenedNotification when I open a contextual menu. I do see the callback for the notification, but it is only after I click away and close the menu. Would anyone have an explanation as to why the menu notification is delayed?
I suspect the runloop needs to be running in the default mode for your notification to be received. Since you're observing the notification in your own process, and menu tracking runs the runloop in a custom mode while the menu is open, the notification is probably delayed until after the menu closes and the runloop resumes running in the default mode.
It would be easier to tell if this is correct if you posted the backtrace that you see in the debugger when your breakpoint on your callback is hit.
-eric
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden