Re: Problem with Applescript on my mac
Re: Problem with Applescript on my mac
- Subject: Re: Problem with Applescript on my mac
- From: JollyRoger <email@hidden>
- Date: Tue, 07 Nov 2000 07:34:15 -0600
on 11/7/00 5:44 AM, Greg Raymond at email@hidden wrote:
>
Hi,
>
>
I'm fairly new to Applescript and have only written a few small scripts. The
>
scripts all work and I have saved them to my desktop. When I open any of
>
these scripts (compiled Apps) it opens my Applescript but my script editor
>
is empty.
>
>
What is happening. If I get info on the script it contains data. RedEdit
>
says there is data in the file.
>
>
I'm using a G4 400, Mac OS 9.0.4, Applescript 1.4.3, CarbonLib 1.0.4
>
>
Any help would be greatly appreciated.
From some earlier posts on the subject:
<----------
[8-9-2000]
Chris Espinosa has reported a serious problem with Applescript
1.4.3z.
"If you downloaded the "Z" (International English) version
of Applescript 1.4.3 from mid-May to early July, it is likely that
you downloaded a corrupted file. (The Software Update mechanism
automatically loads the version corresponding to your operating
system, so if you have an International English version of
Mac OS 9 and performed a Software Update to Applescript 1.4.3,
you would have received the corrupted software).
If you have experienced the problem where you compile scripts,
run them, save them and when reloaded they show no text in the
Script Editor, you have the corrupted version.
Unfortunately, scripts created with the corrupted version can
not be recovered; it is as if they have been saved as "run only".
We have posted a corrected version of International English
Applescript 1.4.3. It is now available at Apple - Software
Updates for Applescript Update 1.4.3"
<----------
Furthermore Late Night Software posted on their site
"Script Rescue" which is supposed to allow you to recover the
source code for scripts damaged by the corrupted version of
Applescript 1.4.3.
I don't know if it performs a trick unique to SD files or will
recover scripts created in other applications.
I was going to suggest using load script, and then coercing the
script object to a string. This will often work with regular
script objects -- the original source at the time of compile
is returned, not a string version of the live object (with
updated properties). I doubt this would work if saved as run-
only. Although I seem to remember getting an error message
if I tried to open a file saved that way, not an empty script.
So it's worth a try. Report back whether you are able to
solve the problem, and say Hi to Edward Ka-Spel and the
Legendary Pink Dots for me! Good luck Eduard.
<----------
HTH
JR