Viewers for PDF, PS, and DVI ⇒ Problem with Adobe Reader 8.0

[Sven]

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.

Example:

• 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:

Code: Select all

handle-pdf.cmd open "C:\somedir\my-output.pdf"

When trying to close a PDF-file it will call the following instead:

Code: Select all

handle-pdf.cmd close "C:\somedir\my-output.pdf"

That should work!

[dmonkey]

Hi,

Unfortunately the programs pdfopen and pdfclose use the DDE interface to open and close .pdf documents, so these will fail in the same way.

[Kris]

Hi All!

There seems to be a problem, if one has installed the 'new' 8.0 Reader
over the 'old' 7.0 Reader. This works for me to remove the problem:

> Uninstall all reader versions (8.0 and 7.0)
> cleaning the adobe reader directory (delete all reader-connected stuff)
> clean install of reader 8.0 (freshly downloaded from adobe)

After this procedure Adobe Reader 8.0 works like a charm

Sorry, after restart of Win XP error happened again

...I think, downgrading to 7.0 and waiting for an update of 8.0 seems
to be the only solution...

Greetings
Kristof

[MartinC]

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.

Example:


* 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:
Code:

handle-pdf.cmd open "C:\somedir\my-output.pdf"

When trying to close a PDF-file it will call the following instead:
Code:

handle-pdf.cmd close "C:\somedir\my-output.pdf"

That should work!

That was a good idea but unfortunately it also crashes Reader as someone else said.

Thanks anyway!

Martin.

[MartinC]

I have seen that WinEdt has a workaround for that problem.

[Sven]

I have seen that WinEdt has a workaround for that problem.

Do you know how this workaround works? Maybe we could implement the same for TXC.

[roman]

Do you know how this workaround works? Maybe we could implement the same for TXC.

I suppose the WinEdt workaround is just opening documents using the [FileOpen(...)] command instead of the combination [DocOpen(...)][FileOpen(...)]. And then they're closing all the documents using [CloseAllDocs()].

[Sven]

I suppose the WinEdt workaround is just opening documents using the [FileOpen(...)] command instead of the combination [DocOpen(...)][FileOpen(...)]. And then they're closing all the documents using [CloseAllDocs()].

Could someone please verify this? Simply do the following:

• Choose menu entry "Output > Define Output Profiles..."
• Select the PDF-profile on the left ("LaTeX => PDF" by default)
• Select the "Viewer" tab on the right
• Change the DDE commands as mentioned above.

[Kris]

Hi Sven,

verified it ... works even after restart

Thanks to roman!

Greetings

Kris

[emissary]

[...] And then they're closing all the documents using [CloseAllDocs()].

This works but is no real solution to the problem. What if you're working on more than one PDF Document and you do not want to close them all?