Content-Type: |
text/plain; charset="us-ascii" |
Date: |
Thu, 31 Mar 2011 03:04:06 +0000 |
Reply-To: |
|
Subject: |
|
From: |
|
MIME-Version: |
1.0 |
In-Reply-To: |
|
Content-Transfer-Encoding: |
quoted-printable |
Sender: |
|
Parts/Attachments: |
|
|
On Mar 30, 2011, at 6:50 PM, Stan Cleveland wrote:
> I have a question that arises from some experimenting I did. We have Macs where I work with three different OSes. Here are the results of attempts to directly and indirectly get a property from a stay-open script applet:
>
Good to know that Apple fixed/broke that. Though it looks like it no longer differentiates between properties and procedures. Previously you could have a property and a procedure with the same name.
> In all cases, whether an error or the property is returned, the stay-open applet seems to respond only when idle and is unresponsive while executing code[1]. So, is this consistent applet behavior or am I jumping too quickly to a conclusion? If one is using this technique, knowing when to expect a response would be helpful.
>
This is the behavior that I remember. Even with Applescript studio you have to get creative to multithread.
-Mark
|
|
|