Tobias Krause wrote:
Yes, I did exactly the same - and it did not work when I tried it last time... First I realized that whitespace in the viewer name are not supported so I changed the name of the viewer binary...
Whitespace is allowed in the path prefix, though. I just installed PDF-XChangeViewer for test purposes. I did the default installation, put the path (including spaces) in the path prefix, and put the name of the .exe file (which contains no spaces) in the viewer slot of the file format. I assume you did this below, since you were able to load the viewer (and generate the URL message).
Just now I tried changing the viewer again (to write a correct answer) and for what ever reason it worked except the thing that PDF-XChange Viewer (http://www.docu-track.com/home/prod_user/pdfx_viewer) does not accept the file path (while it does if it is the system standard for PDFviewing): it say "Invalid URL". But since I set PDF-XChange Viewer just for testing purpose I don't care at the moment - but it's still kind of weird: where is the difference in the ways LyX calls the viewer?
The problem in this case is that LyX uses Unix-style separators (/) in the file path. Windows understands these correctly, so most applications work, but for some reason PDF-XChangeViewer chokes on them. I verified this by starting PDF-XChangeViewer from the command line, giving it the path to the temp buffer PDF file (in quotes). With DOS separators (\) it works, with Unix separators it gives the URL message.
If you ultimately settle on a viewer that has this problem, one solution would be to set the viewer field in the LyX file format entry to a batch file that converts the path and then invokes the viewer. This would be easy to do if you have sed installed. (The GnuWin32 version is a free download.)
/Paul
