No Windows shell integration if using Adobe Reader

asilbaugh / pdfbinder

Automatically exported from code.google.com/p/pdfbinder

0 stars 0 forks source link

No Windows shell integration if using Adobe Reader #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. On a Windows installation with Adobe Reader as the default action 
for .pdf files, install PDFBinder using the Windows installer.

What is the expected output? What do you see instead?
"Add to PDFBinder..." should be added as an option in the context menu 
for .pdf files. It does not show up. Looking in the registry, the key is 
written as expected, but apparently Adobe Reader somehow overrides the 
behaviour.

Original issue reported on code.google.com by jsr%mala...@gtempaccount.com on 16 Jun 2009 at 2:21

GoogleCodeExporter commented 9 years ago

Original comment by jsr%mala...@gtempaccount.com on 22 Jan 2010 at 9:18

Added labels: Milestone-Release1.1, Priority-Medium
Removed labels: Milestone-1.1, Priority-High

GoogleCodeExporter commented 9 years ago

Original comment by jsr%mala...@gtempaccount.com on 29 Jan 2010 at 10:38

Added labels: Milestone-Release1.2
Removed labels: Milestone-Release1.1

GoogleCodeExporter commented 9 years ago

Original comment by jsr%mala...@gtempaccount.com on 29 Jan 2010 at 10:39

Changed title: No Windows shell integration if using Adobe Reader

GoogleCodeExporter commented 9 years ago

Original comment by j...@malamute.dk on 15 Dec 2011 at 9:36

Added labels: Priority-Low
Removed labels: Milestone-Release1.2, Priority-Medium

GoogleCodeExporter commented 9 years ago

Original comment by j...@malamute.dk on 6 Jul 2012 at 10:17

Changed state: Fixed
Added labels: Milestone-Release1.3