Re: Folder Actions Behavior
Re: Folder Actions Behavior
- Subject: Re: Folder Actions Behavior
- From: email@hidden
- Date: Sat, 28 Jul 2001 16:32:21 EDT
In a message dated Wed, 25 Jul 2001 23:12:09 -0400, Marc K. Myers responded
to Eric Schult:
>
As you've determined, the triggering of folder actions depends on moving
>
items in or out of the folder in the Finder. Scripted additions or
>
deletions won't do it, nor will creation of a new file in the folder.
This is not universally true. I have created new text files using read/write
commands in a CGI, and had successful post processing occur via a Folder
Action (MacOS 9.04). While Marc's workaround suggestion is perfectly valid, I
suspect Eric's trouble is coming from some other source.
Jeff Baumann
email@hidden
www.linkedresources.com
In a message dated 7/26/01 12:10:38 AM, Eric Schult wrote:
>
> I'm using Folder Actions and Folder Actions Plus, but I'm a little bit
>
> stumped by the behavior I'm getting.
>
>
>
> I've attached a Folder Action script to several EPS folders on a network
>
> volume so that when a folder item is added to any one of the EPS folders
>
> (whether or not the folder is open in the Finder) the script launches. If
>
> the new folder item is an EPS, it's copied to a Distiller hot folder for
PDF
>
> conversion.
>
>
>
> The script works fine if I add the EPSes from my Mac (where the Folder
>
> Actions script resides). However, when a remote computer adds the item, the
>
> script doesn't launch. I'd thought the copying of an EPS from any location
>
> would trigger the Folder Action, but apparently it's the (local) action of
>
> copying to the attached folder that's the trigger, not the (remote)
physical
>
> addition of a new item that does the trick. (A rather fine distinction, if
>
> you ask me.)
>
>
>
> Can anyone suggest an alternative that would do what I want? My script
>
> follows, hopefully without scrambling the line breaks.
And Marc K. Myers responded:
>
As you've determined, the triggering of folder actions depends on moving
>
items in or out of the folder in the Finder. Scripted additions or
>
deletions won't do it, nor will creation of a new file in the folder.
>
>
I'd handle this by creating a stay-open script with an idle handler that
>
would check your folder periodically for any contents. If it found
>
files it would process them and move them to another folder, leaving
>
your "input" folder empty for the next cycle.
>
>
Marc K. Myers <email@hidden>
>
http://AppleScriptsToGo.com
>
4020 W.220th St.
>
Fairview Park, OH 44126
>
(440) 331-1074
>
>
[7/25/01 11:11:50 PM]