On 01/11/2018 21:59, Richard Kimberly Heck wrote:
On 11/1/18 4:39 PM, Daniel wrote:
On 2018-11-01 20:50, Andrew Parsloe wrote:
On 2/11/2018 1:33 a.m., Daniel wrote:
On 01/11/2018 13:13, Kornel Benko wrote:
Am Donnerstag, 1. November 2018 12:56:08 CET schrieb Daniel
<xraco...@gmx.de>:
I am still getting the "No PDF viewer installed" error message when
"pdfview" is selected as Viewer. I am a bit lost whether this
should be
fixed by now or not in 2.3.1. I saw that the "pdfview" option is
missing
in current master. Maybe that will be the "fix"?
Daniel
As far as I can see, configure.py checks for pdfview. See
configure.py:716
The only reason I can imagine is, that it is not found in searched
PATH.
Kornel
It seems that pdfview itself is the problem. When I execute it, I
get the exact same error dialog.
Probably worth mentioning: I have a number of PDF viewers installed
including Adobe Reader and SumartaPDF.
Daniel
Using 2.3.1-1 on windows 7, the problem is fixed on my system. It
requires a system-wide association of .pdf filetypes with a viewer
(Sumatra in my case, but I changed it to Adobe reader to test and
that worked too). I (dimly) remember Riki doing something about
pdfview for 2.3.1-1.
Andrew
I actually have neither Adobe nor Sumatra as default reader but Edge
(I know...). I'll try tomorrow whether this makes any difference.
What pdfview is SUPPOSED to do is find out what viewer is installed for
PDF files and then do magic tricks if it's Acrobat, but otherwise just
launch that viewer. For whatever reason, the system call to do this
fails on Windows 10 unless some viewer has been explicitly configured.
(I.e., if there's just a 'default' viewer, then it seems we get nothing
back.) Presumably there's some new system call that can be made here,
but I would not know what it is. That's the problem.
Maybe we should try writing something in Python to do this.
Riki
Okay, I tried with a couple of readers as default. Adobe Acrobar Reader
DC, SumatraPDF, Foxit Reader, PDF-XChange Editor, Firefox, Chrome, and
Opera set as default for pdf files works as expected. So it's not as bad
as I first thought. However, these are all non-Store apps but none of
the Store apps I tried work: Microsoft Edge (Windows 10 default), Foxit
Mobile, and Adobe Reader Touch are not recognized and no fall back is
used so one gets the error message.
(Just to my defence: I am using Edge as default because it is the least
bad app when it comes to overall pen input pdf experience. It's still
awful but the others are worse in my experience.)
Daniel
