Problems with printer HP LaserJet 2420 - inputbin Tray 2
Posted: Wed Jun 25, 2014 7:35 am
On "HP LaserJet 2420" printer, user can select Tray 2 as input bin in printing dialog, but this input bin isn't used for printing anyway.
Even if this tray is selected as default input bin in the OS settings, PrintWithWpf sends report to the Tray 1.
The possible core of the problem is that PrintDialog returns PrintTicket.InputBin as InputBin.Unknown.
There are articles and blogs confirming that this is WPF problem (not Stimulsoft in origin) and that WPF propagates only standard input bins (based on this enumeration).
I just ask you, if it's possible to implement hack similar to one described here:
http://social.msdn.microsoft.com/Forums ... windowsxps
which would be able to replace InputBin.Unknown by Tray 2, or another tray proposed by StiOptions settings (to allow programmers decide which input bin they want to print from).
Option 2: Propose the solution how to implement it in our code (when to modify the PrintTicket). To point us to sample code, simple demo, etc. We would be grateful!
Option 3: Fix the problem entirely (which I guess isn't possible right now).
Whichever way, thank you for your response.
Even if this tray is selected as default input bin in the OS settings, PrintWithWpf sends report to the Tray 1.
The possible core of the problem is that PrintDialog returns PrintTicket.InputBin as InputBin.Unknown.
There are articles and blogs confirming that this is WPF problem (not Stimulsoft in origin) and that WPF propagates only standard input bins (based on this enumeration).
I just ask you, if it's possible to implement hack similar to one described here:
http://social.msdn.microsoft.com/Forums ... windowsxps
which would be able to replace InputBin.Unknown by Tray 2, or another tray proposed by StiOptions settings (to allow programmers decide which input bin they want to print from).
Option 2: Propose the solution how to implement it in our code (when to modify the PrintTicket). To point us to sample code, simple demo, etc. We would be grateful!
Option 3: Fix the problem entirely (which I guess isn't possible right now).
Whichever way, thank you for your response.