Sven wrote:Hi Martin, I don't know anything about "pdfopen" and "pdfclose", but if these are simple command line tools, you can make TXC to call them instead of executing a DDE command. Simply do the following:
I have to correct myself: The above does not work. What you can enter in "Command line argument" edit box are not whole programs to be executed, but only special command line parameters to the executable specified with the "Path of executable" edit box at the top of the "Viewer" page. When TXC is about to recreate output it will execute the executable with the specified command line arguments to close the document.
If you really do have special command line tools like "pdfopen" and "pdfclose" a workaround using a script file (i.e. a Windows batch file) should work.
- You create a batch file called "handle-pdf.cmd" which accepts two parameters: The first parameter has to be one of the two strings "open" or "close". The second parameter has to be the path of the PDF-file to be opened or closed. Depending on the first parameter, your script has to decide whether it should call your "pdfopen" or your "pdfclose" tool.
- On the viewer page in TXC you specify the path to your batch file as the executable (top of the page).
- On the viewer page in TXC enable the "Command line argument" option for the open and close command.
- For the open command you specify the following command line argument: open "%bm.pdf"
- For the close command you specify the following command line argument: close "%bm.pdf"
When trying to open a PDF-file, TXC will now execute the following command:
When trying to close a PDF-file it will call the following instead:
That should work!