During implementation we learnt that a slightly different strategy with the public keys is of advantage.
The driver can check the value of any feature attribute any time, at least in theory.
The driver knows the interface to the operating system and the applications best as well.
So it does not seem right to create public keys for platform settings (like provided in a devmode structure under Windows). An example is DRV_Copies, which had been created as a public key. This entry is removed from the list.
Any driver has to check if a driver's feature is overwritten by the application's job setting. This may vary a lot from platform to platform.
With the sample of copies the driver knows the setting of copies in the driver's user interface, but has to check, if the application is sending a print job with a different copy setting, which would have a higher priority than the setting in the driver's UI.
Comments?
Changed, not yet on the web site.
Norbert Schade
69 Prescott Drive
North Chelmsford, MA 01863
978-251-1017
norbertschade@attbi.com
This archive was generated by hypermail 2b29 : Mon Apr 01 2002 - 12:36:16 EST