Re: Writing a more usable AppleEvent logger
Re: Writing a more usable AppleEvent logger
- Subject: Re: Writing a more usable AppleEvent logger
- From: Jean-Daniel Dupas <email@hidden>
- Date: Wed, 19 Nov 2008 14:52:58 +0100
Le 19 nov. 08 à 13:36, Ken Tozier a écrit :
On Nov 17, 2008, at 3:51 AM, Jean-Daniel Dupas wrote:
Le 17 nov. 08 à 08:06, Ken Tozier a écrit :
What do you mean by "this tool" ? export is used to set an
environment variable. I guess that system functions that send and
receive event just check if the env var is set and log appropriatly.
To actually log events, you have to launch an app from the terminal,
so I suspect something is going on in the background to trap events
before sending them on to the target. Basically, I'm looking either
to replicate this trapping or to register for notifications (if
that's possible) on AppleEvents of external
apps._______________________________________________
As I said, you don't have to execute any tool to log events, you just
have to set environements variables. You can do this in Xcode
executable configuration, using the Terminal, etc.
No external tool involved in the process.
The logging is performed by the application itself (I guess this is
done in AESendMessage or a lower level private function for send
events and in AEDecodeMessage or a lower level private function for
received event).
_______________________________________________
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