• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Script Editor 1.6 problems ...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Script Editor 1.6 problems ...


  • Subject: Re: Script Editor 1.6 problems ...
  • From: John Cooper <email@hidden>
  • Date: Thu, 2 Aug 2001 15:44:28 -0700

On 2001.08.02, Michelle Steiner wrote:

On 8/2/01 8:16 AM, harry brindley <email@hidden> wrote:

I'm having this problem with Script Editor 1.16 under Mac OS 9.1 on
an iBook where ...

1. The text in my Format button in my Save dialog is often corrupted
and, quite often ..
2. If I double click a script to open the Script Editor, all the
menus and their pull down items are similarly corrupted (although if
I launch the Editor first and then file>open the script the menus are
not corrupted, just the Format button mentioned in para 1 above.

Anybody else notice this, know why and how to fix?

It's because for some reason, the Finder has made one of the
foreign-language versions of Script Editor in Mac OS X the default
application--and that application (as are all of the OS X
foreign-language versions) is inside a package. I had to stuff the
entire folder containing those packages, delete the folder, and delete
the foreign-language prefs file, then rebuild the desktop, to get things
working properly.

Yes, the iBook is launching the Japanese OS X Script Editor. My iBook did the same thing.

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.

--
John Cooper


  • Follow-Ups:
    • Re: Script Editor 1.6 problems ...
      • From: Greg Strange <email@hidden>
References: 
 >Re: Script Editor 1.6 problems ... (From: Michelle Steiner <email@hidden>)

  • Prev by Date: Re: What does "Finder could not get folder..." mean? (tell block abuse)
  • Next by Date: Re: Startup Disk scripting (redux)
  • Previous by thread: Re: Script Editor 1.6 problems ...
  • Next by thread: Re: Script Editor 1.6 problems ...
  • Index(es):
    • Date
    • Thread