Looking like an OS bug (Was NSAppleEventManager stops recieving events)
Looking like an OS bug (Was NSAppleEventManager stops recieving events)
- Subject: Looking like an OS bug (Was NSAppleEventManager stops recieving events)
- From: Fabian Lidman <email@hidden>
- Date: Mon, 24 Jan 2005 15:29:02 +0100
Hello again,
It seems like compiling an NSAppleScript which refers to the calling
application makes the NSAppleEventManager go "blind". Can anybody
confirm that this is a bug in the AppKit?
Hello people,
Q: What could cause NSAppleEventManager to suddenly stop recieving
apple events?
Sorry if anybody thinks this is off-topic for the Cocoa list. I tried
asking this question at the applescript developer list a while back,
but recieved no response.
I am using the new-ish NSAppleEventManager class to make my
application scriptable. At startup, the proram install four different
event handlers. I also catch
NSAppleEventManagerWillProcessFirstEventNotification for debug
purposes, and NSLog a little "hello world" message in its handler.
The application recieves apple events just like it's supposed to,
until i open a document. Then the debug log is suddenly silent, and no
new events are recieved (leading to a vague error on the applescript
side -- the variable somethingIJustAssigned is undefined). I do not
use Cocoa's document architecture. Documents aren't necessarily opened
in a new window, they may just populate a few views in a single
window. Opening a document doesn't install any new apple event event
handlers.
Anybody got the slightest clue what could be stopping events from
reaching the AE manager?
_______________________________________________
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