Re: Script losing their paths to Standard Additions
Re: Script losing their paths to Standard Additions
- Subject: Re: Script losing their paths to Standard Additions
- From: email@hidden
- Date: Mon, 13 Aug 2001 12:52:18 -0400
On 10 Aug 2001 08:57:44 -0600, Lyle Petro <email@hidden> wrte:
>
I am hoping someone can help me with a rather baffling problem (for me
>
anyway). I have a number of scripts that are running on many Macs
>
here. [...] On most of the
>
machines, this has proceeded with no problem. On a few however, the
>
scripts have started to behave erratically. Occasionaly when they run,
>
they will display an error such as "<<script>> doesnt understand the
>
<<earslvol>> message". If I click OK and try again, the error comes up
>
again and again. However if I click edit and thereby bring up the
>
script in Script Editor, the offending command is highlited.
>
Confusingly, to me, the offending command is displayed as "current
>
date". I would have expected it to display raw event codes if this was
>
a problem. Yet, I know this is in the Standard Additions, so it should
>
always be available (and yes, it is in the Scripting Additions folder of
>
the offending Mac). If after opening the script in Script Editor, I
>
simply close Script Editor, the scripts run fine. Any ideas. Thanks.
No ideas, but I've seen the same thing on my system. I think there might be
some relationship with upgrading or downgrading the version of AppleScript,
since that was what I was doing when the problem occured. I haven't been able
to reproduce it, and just dismissed it as transient weirdness until I read this
posting.
In my case, I'd upgraded AppleScript to 1.6, ran into problems with the sending
of handler calls to a script application, and downgraded AppleScript itself to
1.5.5. But I didn't downgrade the Script Editor, Standard Additions or other
Apple components in the Scripting Additions folder. So that might be the cause.
Now, I can't reproduce the problem (it went away on recompiling), but I'll keep
my eyes open for any other older scripts I have to see if they do the same
thing. Unfortunately, I can't supply any more detail, such as what event or
what command caused it. I remember I got "<<script>> doesn't understand the
<<event xxxxxxxx>> message" but I didn't note what the event was.
--
Scott Norton Phone: +1-703-299-1656
DTI Associates, Inc. Fax: +1-703-706-0476
2920 South Glebe Road Internet: email@hidden
Arlington, VA 22206-2768 or email@hidden