Currently Being ModeratedApr 3, 2013 9:20 AM (in response to Gerben Wierda)
Currently Being ModeratedApr 3, 2013 9:35 AM (in response to pjdube)
That almost did it. What was needed was to set 'ignore input' on a few actions or the result ended up in some temp directory somewhere deep in the system. Otherwise, the target directory was the temp directory that PDF to JPEG uses.
What is now left as a problem is that this temp directory (that is reused seemingly) still has a few copies of the jpeg, so if I act on foo.pdf I get foo-3.jpeg. I can remove those now as the above says where it is, but if I ever get a problem it will be difficult to find the temp directory to clean stuff out. I can't think of an wasy more robust flow.
Currently Being ModeratedApr 3, 2013 9:41 AM (in response to Gerben Wierda)
Ok. Can you post your whole workflow now so I can see what to debug?
I am attaching the workflow I did here for you to download and see where we differ, as this works for me.
Currently Being ModeratedApr 3, 2013 1:18 PM (in response to pjdube)
Our work flows are identical. It works for me too. But during development, when the 'ignore input' flags were not properly set, the final move failed (because it moved the file upon itself). A second call the lets PDF to JPEG create a 'duplicate' file name, e.g. foo-1.jpeg. This one keeps sitting in that temp directory and messes things up.
Removing the stray jpegs from the directory lets the flow work properly.
Currently Being ModeratedApr 3, 2013 2:10 PM (in response to Gerben Wierda)
Ok, so I tested yours... and... everything worked perfectly!
Unless I am mistaken on what you are trying to do exactly. I ran your Service on a PDF that was in a Folder on my desktop and the below is the result. I actually ran it on a BIG PDF to make sure that it worked.
See below. And let me know if you are trying to do something else exactly, or maybe there is some other bug that is not allowing you to run the service.
Currently Being ModeratedApr 3, 2013 10:45 PM (in response to pjdube)
Yes, as I said, mine works fine too.
The effect I was looking at was the result of it running a few times when it was not OK yet. Probably you can get the same effect by running it once or a few times on the same PDF file without the last step. Then run it again on the same PDF file.
It only happens when something has gone wrong (which was the case during development).
Currently Being ModeratedNov 20, 2013 1:55 PM (in response to Gerben Wierda)
Gerben and Pjdube-
I have read through this thread and am interested in getting a look at the workflow's you created (wherein you both stated arriving at the same structure and results).
This is my first attempt at Automator and I am looking to either combine multiple existing PDF's or input an Adobe form filled pdf and convert to a pdf which lacks field controls.
Particulary how are outputs from each item in the workflow passed to the process as a whole or "ignored"?