S
stpwd
Guest
Hi,
we are currently using an in-house developed port monitor with a pscript minidriver using the v3 printing model.
The port monitor basically collects information about the print job and runs a GUI application in the current user context.
According to the API documentation for XcvData() and friends, using third-party port monitors is deprecated.
There is a thread in this forum suggesting to write a custom v4 rendering plugin, but according to the document "Best Practices for Developing Printer Drivers" rendering code must never display a user interface.
Another suggestion is to use a file port with an already configured file name. This is no viable solution as we are dealing with private data in a high-volume environment.
What would be the "correct" way to implement this in the v4 model?
Cheers,
Stephan
Continue reading...
we are currently using an in-house developed port monitor with a pscript minidriver using the v3 printing model.
The port monitor basically collects information about the print job and runs a GUI application in the current user context.
According to the API documentation for XcvData() and friends, using third-party port monitors is deprecated.
There is a thread in this forum suggesting to write a custom v4 rendering plugin, but according to the document "Best Practices for Developing Printer Drivers" rendering code must never display a user interface.
Another suggestion is to use a file port with an already configured file name. This is no viable solution as we are dealing with private data in a high-volume environment.
What would be the "correct" way to implement this in the v4 model?
Cheers,
Stephan
Continue reading...