• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Main Event queue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Main Event queue


  • Subject: Re: Main Event queue
  • From: David Blanton <email@hidden>
  • Date: Wed, 5 Aug 2009 10:22:17 -0600

You need to do remote debugging, you can look up how to accomplish this, I did it some years ago and don't remember.

Look at the Cocoa and Carbon APIs and make educated guesses as to what would be called when for example, a contextual menu is to be displayed.

Set a break point on that API.

Perform the action on the target machine and see if it hits. If not make another guess. You will be surprised how quickly you can home in on correct API.


I did this years ago building a DRM KEXT and could trap, in one example all print operations from all applications.


Good luck!

db







On Aug 5, 2009, at 9:42 AM, Ken Thomases wrote:

On Aug 5, 2009, at 9:50 AM, Sandro Noel wrote:

what I would like to do is broad range, get information about every action for every application in my current desktop session.

Window movement, hide, show, activate, deactivate, open, close, mouse movement, drag and drop operations, contextual menus pop-up.
I want to know everything.


Raw mouse movements, or mouse clicks are of little interest, so are keyboard events.
What i am interested in is the action happening after a mouse movement or click, or keyboard shortcuts, menu selections has happened.
anything that influences display of content on the desktop.

Hmm, I don't think you can quite achieve that.

Event taps can only give you the low-level events like mouse clicks and key presses.

The individual frameworks (Carbon and Cocoa) are responsible for interpreting those events into the higher-level behaviors you're talking about. And that generally occurs inside of individual application processes, not centrally in the window server where event taps operate.

You might look into the Accessibility API. That can probably give a richer description of what's happening, although perhaps not as rich as you're hoping.

Regards,
Ken

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please 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



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please 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


References: 
 >Main Event queue (From: Sandro Noel <email@hidden>)
 >Re: Main Event queue (From: Ken Thomases <email@hidden>)
 >Re: Main Event queue (From: Sandro Noel <email@hidden>)
 >Re: Main Event queue (From: Ken Thomases <email@hidden>)

  • Prev by Date: Re: Core Data completely unable to find the source object model for migration
  • Next by Date: Re: Generating random numbers
  • Previous by thread: Re: Main Event queue
  • Next by thread: Re: Main Event queue
  • Index(es):
    • Date
    • Thread