Re: applescript-users digest, Vol 2 #280 - 14 msgs
Re: applescript-users digest, Vol 2 #280 - 14 msgs
- Subject: Re: applescript-users digest, Vol 2 #280 - 14 msgs
- From: email@hidden
- Date: Fri, 26 Jan 2001 11:07:38 -0800
>
>>>> It takes the Finder so long to move or copy a file that it doesn't
yet
>
exist in the new location when the script moves on, so the script errors.
>
>
OK, the finder does what it does the way it does it. In other words,
when
>
it copies files it does it the same way from the Scripting interface as
the
>
user interface. It doesn't take any longer. If that's not good enough,
if
>
you're in a hurry and don't care about progress bars and don't mind your
>
machine not doing anything else until the files are done copying, then
use
>
Jon's commands or one of the others.
It's not me, Ed. I'd gladly wait a second or two. But the SCRIPT doesn't
wait: having issued its command to the Finder, it then goes on to the next
commands - the next lines of the script - which expect to find the file in
its new location. Presumably when all the commands are in a Finder tell
block, things work OK. But when these next commands go to some other
application (or none) and they attempt to act on file that they can't find,
the script errors, then times out a minute later. So nothing works at all.
Honestly, I couldn't care less if it took another 2 seconds. But having a
script fail, especially when it's working automatically with no one around
to click dialogs and try running it again, is no good at all. The whole
thing is kaput. That's what I've been talking about, off and on, for a few
months now. This is not an unreasonable complaint, and I'm glad that osaxen
like Akua and Jon's can solve the problem.