Re: NSAppleScript not in the main thread
Re: NSAppleScript not in the main thread
- Subject: Re: NSAppleScript not in the main thread
- From: Nathan Day <email@hidden>
- Date: Thu, 1 Jun 2006 13:07:46 +1000
Yes, but in practice it doesn't matter, you can filter all the
AppeEvent directed to your own application and only send them in the
main thread, and when your main thread handles an AppleEvent it
either only block very briefly so the user does not notice it or its
for something like display dialog, in which case you are wanting for
the user to supply input.
The point is it does not block for the entire duration of your script.
On 31/05/2006, at 12:42 AM, Daniel Jalkut wrote:
That's interesting - but doesn't that present the undesirable
behavior of an AppleScript blocking on the main thread (while
waiting for an AppleEvent reply). Isn't that one motivation for
moving it to a separate thread in the first place?
Daniel
On May 30, 2006, at 10:18 AM, Nathan Day wrote:
My ComponentInstance class than comes with NDAppleScriptObject
allows you to catch every NSAppleEvent that the AppleScript
attempts to send, you can then resend it yourself in the main thread.
Nathan Day
email@hidden
http://homepage.mac.com/nathan_day/
_______________________________________________
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