Re: Applescript coding
Re: Applescript coding
- Subject: Re: Applescript coding
- From: Nigel Garvey <email@hidden>
- Date: Sun, 24 May 2015 12:00:20 +0100
I wrote on Tue, 19 May 2015 19:59:20 +0100:
>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.
It seems things aren't quite as bad as I remembered in this respect — in
Yosemite, at least. Script Editor _tries_ to compile any uncompiled
changes before saving. It only saves scripts containing uncompiled
changes if they can't be compiled AND the saves are part of its quit
process. That could sometimes actually be quite helpful.
>• 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.
I came across a tip on Friday for turning off autosave in individual
applications:
<http://apple.stackexchange.com/questions/27544/how-to-completely-disabl
e-auto-save-and-versions-in-mac-os-x-lion>. Applying it to Script Editor
by running the following in Terminal (with Script Editor not open) …
defaults write -app 'script editor' ApplePersistence -bool no
… seems to have cured many of the other problems.
• Edits are now only saved when I save them and the system doesn't
interfere with the files or their modification dates inbetweenwhiles.
• There's no attempt to save changes while a script's running.
• When Script Editor's quit, it offers all unsaved scripts for saving,
even when none of them have been saved before and the front window's a
dictionary window.
There are further joys in that:
• "Save As…" has been restored with its original keyboard shortcut in
the "File" menu.
• The individual "Do you want to save…?" dialogs are all of the older
type with the convenient, one-handed, Control-D shortcut for "Don't
Save".
>Yep. Script Editor's very hard work now.
Not quite so much now. :)
NG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden