>On the console display, there are interesting questions...
Another interesting (similar) question is that the MIB
does not indicate what to do when the text message simply
overruns the console buffer. There are various methods
applied like "marques" or "alternate". There is currently
no way, in the MIB, to indicate that the printer is
applying such a method.
Except for "fidelity"... which method the device actually chooses may not be
of great concern. But I've seen management GUIs actually truncate when
prtConsoleDisplayBufferText overruns prtConsoleNumberOfDisplayChars.
Harry Lewis
IBM Printing Systems
harryl@us.ibm.com
Ira McDonald <imcdonal@sdsp.mc.xerox.com> on 07/20/99 08:33:15 AM
To: HPARRA@novell.com, hastings@cp10.es.xerox.com, ipp@pwg.org, Carl
Kugler/Boulder/IBM@IBMUS
cc:
Subject: RE: IPP> IPP Implementation Questions [spooling strategies]
Hi Hugo,
I agree that these are both interesting attributes (although
in the matter of the console display buffer I wonder where we'll
draw the line to duplicate Printer MIB objects in IPP).
And keywords for timers are *not* a good idea. Separate
integer attributes for timers or max table dimensions
(ie, max jobs) are more appropriate.
On the console display, there are interesting questions about
what's in the console buffer array when the local UI is a
full GUI. For Xerox printers, I've suggested that at least
the 'title' of the current GUI screen plus at least one
'status line' are appropriate for GUI-based local UI in
the Printer MIB.
Cheers,
- Ira McDonald
High North Inc