Print Finder Items action completes but doesn't do everything
Print Finder Items action completes but doesn't do everything
- Subject: Print Finder Items action completes but doesn't do everything
- From: Rush Manbert <email@hidden>
- Date: Thu, 24 Jan 2008 15:48:48 -0800
I am running on 10.4.11.
I am trying to put together a workflow that will print a bunch of (user
selected) OmniGraffle files as PDF, then move the PDF files into the
same folder as the graffle source files.
To do this I set up a CUPS-PDF printer using the package available from:
http://www.codepoetry.net/projects/cups-pdf-for-mosx
The printer seems to work perfectly if I just print to it from within
OmniGraffle. It puts all of its output into a cups-pdf folder on the
desktop, which it creates as necessary.
My workflow does the following:
1) Find the cups-pdf folder on the desktop (There may not be one)
2) Archive the folder
3) Delete the folder
4) Let the user select the files to be converted to PDF
5) Print all the selected files to the CUPS-PDF printer by using the
Print Finder Items action
6) Run a shell script that waits for all of the output files to be
generated. It gets the original list of files that need to be converted
as its argument list. It counts the number of arguments, then polls the
~/Desktop/cups-pdf directory until it contains the same number of *.pdf
files. Once enough PDF files have been created, it copies all of them
back to the directory that contains the graffle source files.
7) Delete the (now empty) cups-pdf folder from the desktop.
This workflow works correctly some of the time. Generally it works when
I don't try to convert too many files. Other times only some of the
selected files get printed as PDF. When I run the workflow in Automator,
it marks the Print Finder Items action as having completed, even when
only a few of the required output files have been generated. When this
occurs, my shell script action hangs forever, and I can examine the
contents of the cups-pdf folder and see that only some of the files are
there. I find this behavior to be very strange, and I couldn't find
mention of anything similar in the archives.
Does anyone have any idea why this might be happening? This is also the
first workflow I have ever written, so debugging tips would also be welcome.
Thanks,
Rush
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Automator-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden