Re: Script Editor 1.6 problems ...
Re: Script Editor 1.6 problems ...
- Subject: Re: Script Editor 1.6 problems ...
- From: david_reynolds <email@hidden>
- Date: Fri, 03 Aug 2001 16:41:29 -0700
on 2001.08.03 10:34, John Cooper at email@hidden said:
>
On 2001.08.02, Michelle Steiner wrote:
>
>
> On 8/2/01 3:44 PM, John Cooper <email@hidden> wrote:
>
>
>
>> An easier and less potentially destructive way to fix the problem is
>
>> to change the English OS 9 Script Editor's creation date so that it
>
>> appears to be the most recent of all the Script Editors present. (The
>
>> Finder always chooses the most recent of conflicting applications on
>
>> the active partition.) I did this with the Snitch utility and have
>
>> had no problems since--although I still see an occasional cosmetic
>
>> glitch, such as an alert message reading 'The %1$@"%2$@" wouldn't
>
>> compile; you won't be able to save it in compiled form, only as text'
>
>> when I tried to save a poorly written script. Since %1$@"%2$@" was an
>
>> excellent way of describing the script in question, I don't have a
>
>> problem with that.
>
>
>
> That's a great idea. I'll keep it in mind if (when) such a situation
>
> comes up again.
>
>
>
> To take care of the glitch that you have, remove the foreign-language
>
> Applescript preferences file from the preferences folder.
>
>
>
> --Michelle
Actually the %1$@"%2$@ message is a bug in Script Editor 1.6.
on 2001.02.27 14:48, Chris Nebel said:
>
Oh, that's a good one. For some reason, the string substitution is failing to
>
do anything, and it's showing you the formatting codes, which happen to look
>
remarkably like curse punctuation.
on 2001.02.27 18:23, Chris Nebel at email@hidden said:
>
It's a problem with Script Editor 1.6 itself, and has nothing to do with the
>
AppleScript or CarbonLib extensions. Due to timing constraints, it's probably
>
going to ship that way.
>
With any luck, everyone else will find it as funny as you did. :)