Chuck said:
I beg to differ. The ops system has the responsibility of going
back to a
known state after an application is closed. Things get complicated
when a
non ops system driver is involved, but that does not relieve the
responsibility. If the ops system can do nothing more than call
the printer
driver with some sort of return to default, it should do so. The
alternative
would be to return to the "dark ages", and have the application
totally
control the printer. Admittedly, the windows only printers and
supporting
software pose a more complex problem than the older text and
graphics
printers.
Isn't that what I said? Earlier versions of Microsoft Word for
Windows or WordPerfect for Windows would change the printer defaults
and even the default printer. In those days each application used
its own print drivers. You might have selected a color printer for
a single page document in Word. When you used another application
to print, you might have used up all of your color ink if you sent
another print job from a networked computer expecting it to use the
normal default laser printer.
When you are using varied operating systems in a workgroup, you do
not know what will happen after print job.
