Re: FolderActions bug?
Re: FolderActions bug?
- Subject: Re: FolderActions bug?
- From: Michael Terry <email@hidden>
- Date: Sun, 25 Apr 2004 18:08:34 -0700
On Apr 25, 2004, at 3:27 PM, John C. Welch wrote:
On 4/25/04 9:14 AM, "Rob Jorgensen" <email@hidden> wrote:
also long for folder actions that do not kick in until newly added
files are complete (files that are in the process of being
downloaded/transferred to the attached folder). It shouldn't be
necessary for scripters to add routines to determine if a
download/transfer is complete.
The problem is, define "done". Is it done when the size doesn't update
anymore? When the thread handling the copy is quit? When the dialog
goes
away?
As well, what of remote processes adding files from different
machines/OS's?
They *can't* set nor unset OS X - specific flags. The don't know about
them.
What about files that are held open by a process until a user action is
completed?
In a modern computing environment, there's no easy answer to "is it
done
copying yet", ESPECIALLY when remote systems are involved. In the end
you
have to figure out what works for you. For my needs, a simple size
comparison on a 3-second delay works. That's part of the fun world of
writing your own code.
and
On Apr 25, 2004, at 2:02 PM, Emmanuel wrote:
At 10:14 AM -0400 25/04/04, Rob Jorgensen wrote:
I also long for folder actions that do not kick in until newly added
files are complete
I'm afraid you'll long long, the only way for Folder Actions to know
that the file is complete would be to include - and run - Photoshop's
code for opening files, wouldn't it.
Although I've never done much with Folder Actions, I've thought about
this problem in passing before, and I'd always thought like Rob: Why
don't Folder Actions wait until the file is ready before activating? I
always figured I'd use 'info for''s 'busy status' property to deal with
it. Isn't it for stuff like this? Why couldn't FA do whatever polling
'info for' does? Even if there are situations where 'busy status' would
be ineffectual, aren't there some where it would be, so scripters doing
those tasks would have an easier time of it?
These questions assume 'busy status' works at all. Is it broken in OS X
or is it not as useful because of the underlying OS architecture? I
seem to remember hearing that it used to be more useful pre-OS X. In
any case, in the few times I've tried it, I don't think I've ever
gotten 'busy status: true', but I may be using it wrong.
Mike
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.