The other thought I had was to keep track of the process id AND the lock state on the file that you hand to the GUI program. My thinking is that if the GUI program is modifying the PDF file you have handed it, it is probably locking it until it is done processing. If that is the case, you might be able to issue a kill to the pid after the lock is removed. Am not sure of how OSX keeps track of processes, or how you kill them off.
Good luck! :-)
...the majority is always wrong, and always the last to know about it...
In reply to Re: Running an external GUI program
by wjw
in thread Running an external GUI program
by mdrisser
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |