Re: Moving
Re: Moving
- Subject: Re: Moving
- From: email@hidden
- Date: Sun, 29 Nov 2009 13:01:14 -0800
> There is a files move command in it.
> It used to work correctly (since 2004 !!), but I had to add some new code lines (not related to this move command).
> I was obliged to change the code from "move" to copy (or duplicate) from folder A to B and then delete the copied A files.
The move command is not terribly reliable. I've been using the duplicate/delete routine since long before 2004.
> The result is the same, but I am a little frustrated to add a new code line, to perform the same operation.
I don't understand why, it's not like you're in the terminal and have to type the command each time your run it.
I've got my version in a handler that I just copy and paste into any script that might need it.
> Should I enclose the moving command in a second nested Finder tell block ?
No, that would not help at all.
A tell block directs all enclosed commands to the application, so, since they're already going to the Finder another tell finder block would be redundant.
(Unless you have a nested tell to a different application, but it doesn't sound like that's the issue.)
ES _______________________________________________
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
| References: | |
| | >Moving (From: ba95 <email@hidden>) |