Re: Saving a property after running a script remotely
Re: Saving a property after running a script remotely
- Subject: Re: Saving a property after running a script remotely
- From: Paul Berkowitz <email@hidden>
- Date: Wed, 11 Sep 2002 13:01:31 -0700
On 9/11/02 7:44 AM, I wrote:
>
If I find that it works reliably when the main script is an applet, would
>
anyone want to know?
The identical main script saved as an applet works perfectly. 100% reliable.
The trigger script does 'run script mainScript', then at the end loads the
main script as a script and stores the new property value in it. Works every
time.
So that means there is a limitation with long scripts being run from Script
Menu, then immediately loaded. They don't always get loaded. That's the bug.
It's not the only bug I've found with long scripts. There's a new one in AS
1.9, where scripts that have more than 32766 (0x7fff) style runs (according
to Mark Alldritt, confirmed by Apple) in the script's decompiled source
code, won't compile in the AppleScript Debugger language (as used by Script
Debugger, but it's actually an OSA language and is part of AppleScript).
It's quite possible that not too much testing of long scripts takes place
because Script Editor can't compile them. I seem to be the testing ground
for these monster scripts.
Let me go on record as saying how robust I find script applications, and how
well the transition to OS X applets has been managed. There.
--
Paul Berkowitz
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.