I seem to remember something about ActiveX_PDFWindow being broken, but it's been a while and I thought I'd give it a try. I opened up the demo on Windows XP (wxPython 2.8.3.0) and tried to open a PDF, but nothing happened.
Can someone confirm that this does or does not work currently? I have Adobe Acrobat 8.0 installed.
There was also some hubbub, as I recall, regarding getting a multi-platform PDFWindow, which would really be the preferred thing anyway. Does anyone have any information on that angle?
I seem to remember something about ActiveX_PDFWindow being broken, but it's been a while and I thought I'd give it a try. I opened up the demo on Windows XP (wxPython 2.8.3.0) and tried to open a PDF, but nothing happened.
Can someone confirm that this does or does not work currently? I have Adobe Acrobat 8.0 installed.
There was also some hubbub, as I recall, regarding getting a multi-platform PDFWindow, which would really be the preferred thing anyway. Does anyone have any information on that angle?
Thanks!
Paul
Paul,
I'm sorry for the long delay in responding to your post. I think I have mentioned somewhere before, I have got seriously behind in following this list due to the pressure of a software release - but I'm now catching up slowly.
Acrobat Reader worked OK using wx.activex for versions 4.0 through 6.0 but version 7.0 crashed. It was discovered that 7.0 could be made to work by using an Internet Explorer interface and controlling Acrobat Reader via that. New classes were added to wx.lib.pdfwin and the appropriate selection made by determining what version of Acrobat Reader is installed.
Unfortunately the get_acroversion() function is currently hard-coded only to detect versions up to 7.0. I guess this needs future-proofing in some way, but the immediate fix to permit Acrobat Reader 8 to be used, for example in the demo, is to modify line 29 in wx.lib.pdfwin to read
for version in ('8.0','7.0', '6.0', '5.0', '4.0'):
I seem to remember something about ActiveX_PDFWindow being broken, but it's been a while and I thought I'd give it a try. I opened up the demo on Windows XP (wxPython 2.8.3.0) and tried to open a PDF, but nothing happened.
Can someone confirm that this does or does not work currently? I have Adobe Acrobat 8.0 installed.
There was also some hubbub, as I recall, regarding getting a multi-platform PDFWindow, which would really be the preferred thing anyway. Does anyone have any information on that angle?
Thanks!
Paul
Paul,
I'm sorry for the long delay in responding to your post. I think I have mentioned somewhere before, I have got seriously behind in following this list due to the pressure of a software release - but I'm now catching up slowly.
Acrobat Reader worked OK using wx.activex for versions 4.0 through 6.0 but version 7.0 crashed. It was discovered that 7.0 could be made to work by using an Internet Explorer interface and controlling Acrobat Reader via that. New classes were added to wx.lib.pdfwin and the appropriate selection made by determining what version of Acrobat Reader is installed.
Unfortunately the get_acroversion() function is currently hard-coded only to detect versions up to 7.0. I guess this needs future-proofing in some way, but the immediate fix to permit Acrobat Reader 8 to be used, for example in the demo, is to modify line 29 in wx.lib.pdfwin to read
for version in ('8.0','7.0', '6.0', '5.0', '4.0'):
I totally forgot that was in there! I'll gladly accept any patches that make this more intelligent about how it chooses which implementation it uses so we don't run into this again when 9.0 is released.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Unfortunately the get_acroversion() function is currently hard-coded only to detect versions up to 7.0. I guess this needs future-proofing in some way, but the immediate fix to permit Acrobat Reader 8 to be used, for example in the demo, is to modify line 29 in wx.lib.pdfwin to read
for version in ('8.0','7.0', '6.0', '5.0', '4.0'):
I totally forgot that was in there! I'll gladly accept any patches that make this more intelligent about how it chooses which implementation it uses so we don't run into this again when 9.0 is released.