Repository navigation
Replies: 2 comments 2 replies
|
Thanks for writing this up, and for checking it against the code instead of guessing. You were right: KillerPDF only registered the open verb, so right-click Print, 1.9.3 registers |
|
The print verbs are in 1.9.3. Right-click Print, A few other print fixes from your notes landed alongside it: Custom scale above 100% and Actual size no longer shrink an oversized page to fit, a page that fills the printable area prints without the thin white edge, and Fit to page turns landscape pages in a portrait job to fill the sheet. Your window position PR (#487) shipped in this release too. I'm curious how it holds up against your daily printing now. |
Uh oh!
There was an error while loading. Please reload this page.
Follow-up to #315, where you asked for the print gaps as use cases.
It's a short one.
I had about ten print gaps logged against 1.7.5, and 1.9 shipped most of them before I wrote this up: reverse order, booklet, poster, and print as image, since printing already rasterises.
I said I'd only send the ones where I could name the job, and that leaves one.
Windows has no print verb for KillerPDF
On 4 Nov a script sending a PDF to our office printer asked Windows how to print it.
Nothing was registered for KillerPDF, so the job went through Acrobat.
--printwould have done it fine, the script just couldn't find it.RegisterFileHandleronly writesshell\open\command, for the ProgID (App.xaml.cs:1933) and bothApplications\keys (:1943).So right-click Print,
Start-Process -Verb Printand mail clients printing an attachment either fail with the #44 error or go to another reader.I added
printandprinttoto a scratch HKCU key and the shell ran both, with the printer name coming through as%2.That's two values on each of the three keys, and uninstall already removes those trees.
I only checked the registry side, on Windows 10, against the v1.9.2 tag.
I haven't built KillerPDF with the verbs added.
Your call on whether it's wanted.
All reactions