Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 27 MAR 2006 11:40:11PM Gerald Lovel wrote:

I am confused by the OIPI Set-Printer/Get_Printer documentation.

The INIT command has to come first before any printing, right, and it is necessary because it defines which printer to use, among other things? The INIT command contains parameter settings for COPIES, PAPERBIN, DUPLEX, and so forth, all of which are documented to produce errors if the printer does not support the feature, right? The documentation clearly states that before attempting a DUPLEX setting, one should use the Rv=Get_Printer("DUPLEX") statement to test for errors. Well, how can this work, if you haven't done a Set_Printer("INIT") yet?

Horse — CART — Horse

I'm sure there is a really good explanation of how this really should work. I just don't see it.


At 28 MAR 2006 12:47AM Bob Carten wrote:

It's how we prove the existence of a benevolent printer …


At 28 MAR 2006 10:45AM Warren Auyong wrote:

FWIW I have noticed that the HP drivers no longer self-configure and detect features like duplexing, additional trays, envelope feeders etc and you have to manually set these in the driver.

An ancient version of JetDirect Admin I have has a feature interogation option which fails miserably 95% of the time even on HP printers contemporary with the software version.


At 28 MAR 2006 01:06PM Gerald Lovel wrote:

Bob,

Thanks. You must have been waiting a long time to tell that joke. Here's another Descartes funny:

Descartes walks into a bar, and sits next to an attractive lady. "May I buy you a drink," he asks? "I think not!" she replies, and promptly disappears.


At 19 APR 2006 05:07PM James Mowbray wrote:

Best bet is to set_printer( 'INIT', … ) with dummy parameters (like outputting to a static file, no preview, etc.), collecting what information you need from the driver using get_printer( … ), then calling set_printer( 'TERM' ) to kill off the dummy job, and set_printer( 'INIT', … ) again to start the real job. I'd recommend doing the query work at form (or frame) initialization, and only redo-ing it if the user changes the printer.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/065eaa242b49162a8525713f001428e8.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1