Re: applescript-users digest, Vol 2 #75 - 8 msgs
Re: applescript-users digest, Vol 2 #75 - 8 msgs
- Subject: Re: applescript-users digest, Vol 2 #75 - 8 msgs
- From: email@hidden
- Date: Tue, 28 Nov 2000 13:45:46 EST
I'm getting to this thread late, so I hope this hasn't already been
covered....
"webguide" is correct is using OneClick's "open" command is a pretty
bullet-proof way of running AppleScript from an OneClick button, and Paul
Berkowitz is correct that the "open" command requires the AppleScript be
saved as an applet. (Otherwise, OneClick launches your script editor and
tries to open the script file!)
There's another technique that was posted on the OneClick list a few months
ago that runs compiled scripts and that also seems bulletproof. The OneClick
script looks like this:
applescript
set x to load script file "disk:folder:file"
tell x to run
end applescript
I've not seen the "failure to close" problem using this approach, and it's a
little faster than opening an applet.
Robert Kyle
Star Tribune
Minneapolis
In a message dated 11/26/00 12:13:20 AM, Paul Berkowitz writes:
>
>
On 11/25/00 10:30 AM, "webguide" <email@hidden> wrote:
>
>
> there'as an extremely simple solution to your problem - use the OC 'open'
>
> command rather than the Applescript command. It doesn't execute as fast
>
> as using 'Applescript' but it's 100%, absolutely reliable and doesn't
>
> suffer the problem you refer to.
>
>
I would have guessed that to use OC's 'open' you'd have to save the script
>
as an applet, which means that it does indeed take time to start up the
>
applet every time. Or is this not the case - will it work with a compiled
>
script too?
>
>
--
>
Paul Berkowitz