Jean-Christophe Helary wrote on Tue, 19 May 2015 21:33:47 +0900:
I guess I'm sticking to Script Editor for now :) I don't dislike it, it
just that it crashes every once in a while
Script Editor does have a fair number of problems at the moment, at
least one of which is deliberate and others are possibly faults in the
systems on which it depends.
• It's possible to save scripts uncompiled.
• Thanks to auto-saving, any trial edit in a script is saved whether you
want it to be or not. Even after reverting to the 'last opened' version,
the file's modification date often remains changed anyway.
• As Shane's already pointed out, auto-saving sometimes kicks in while a
script's running, with time-wasting results.
• If the toolbar buttons are customised as text only, clicking any of
them reverts them all to icons and text instead of carrying out the
button's action. This was annoying enough to get me to sign up as a
developer and report it last October, but there's no indication so far
that my report's even been read.
• AppleScript formatting occasionally reverts to the defaults,
disregarding the user's preferences for no obvious reason. I've not been
able to pin down the cause, but I've recently found I can reliably
induce it by doing anything which makes the 'choose application' dialog
appear, such as deliberately calling it in a script or misspelling an
application name. The default formatting appears next item Script
Editor's opened.
• If an .sdef window's frontmost when Script Editor's quit, and none of
the open script documents behind it have ever been saved, you're not
asked what you want to do with them. Script Editor just quits and the
documents reappear next time it's opened.
Yep. Script Editor's very hard work now.
NG