Re: How to deal with Asynchronous Finder operations
Re: How to deal with Asynchronous Finder operations
- Subject: Re: How to deal with Asynchronous Finder operations
- From: Dave Lyons <email@hidden>
- Date: Mon, 19 Sep 2005 17:16:40 -0700
Finder's "duplicate" and "move" operations *do* block the script. As
Chris N says, it's a bug when this doesn't happen.
I have bug reports for "delete" and "empty trash" failing to block,
and the workarounds discussed seem reasonable.
If there are other Finder operations that fail to block your script,
please send me the details (or file a bug at bugreport.apple.com).
Cheers,
--Dave (who works on Finder)
On Sep 15, 2005, at 11:14 PM, Kumar Shailove wrote:
Hey Guys,
Thanks for your valuable responses, the below mentioned scripts are
fine
when dealing with Trash, but since in my script, I am concerned about
many of the Finder operations (copy, move, and delete typically)
from a
folder to Trash, or possibly, from one folder to another; and
sincerely
speaking - there is a larger number of such folders spread over my
local
disk as well as over the network, so I can't hard code the paths of
all
the folders as well. I just search for a set of folders satisfying a
predefined search criterion and then proceed with different File-
Folder
operations.
What I am looking for a generic AppleScript statement which may
give me
such a level of flexibility to wait and watch on when that particular
operation gets completed and then only proceed with the next
AppleScript
statement (because the further statements are strictly dependent on
the
contents of these folders).
Thanks.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden