printer driver settings

Hi

I've a little problem to understand what DrvConvertDevMode,
DrvDocumentPropertySheets and DrvDevicePropertySheets have to do.
So lets start with the question about DrvConvertDevMode. If you get the
parameter CDM_DRIVER_DEFAULT, what does this mean? You have to return the
default values. Are the default values the "manufacturer default values", so
fixed values, that I can specify, or is this the values, that someone set,
by configuring the printer? (so the default settings for this machine, the
all users settings?).
Next question, about DrvDocumentPropertySheets... what's the "internal
DEVMODE structure" ? Is this the default structure for this user? Or for the
calling application? Or are this just the current settings for the current
process? Do I have to store them somewhere? Why?
And a more general question... who is responsible for storing the systemwide
default settings? Is this my driver? Is the "internal DEVMODE structure"
what represents those settings?
And the last question: I always thought, that this is the way it has to go:
1) the application sets the current DEVMODEW structure by calling
DrvDocumentPropertySheets with DM_IN_BUFFER 2) the application lets the
driver to show the propertypages by calling DrvDocumentPropertySheets with
other parameters and 3) the application reads the changed DEVMODEW structure
by calling DrvDocumentPropertySheets with DM_OUT_BUFFER ... but then I saw
the line 855 in docprop.c (msplot sample of the ddk 3790) ->
pPI->pPlotDMOut = (PPLOTDEVMODE)pDPHdr->pdmOut; ... it stores a pdmOut
Pointer... and when applying changes, it directly stores the data into this
buffer... but I never saw this documented... can someone explain me how this
works?



thanks a lot

MR - Rudolf Meier

vipin
Wed Apr 06 23:20:53 CDT 2005

If you feel we should get offline, you can reach me at this address:-
vprnt at lycos dot com

You have asked lot of questions which I doubt you would get in a newsgroup.
Thanks
Vipin

"Meier Rudolf" <meiru@gmx.net> wrote in message
news:ev29SU%23KFHA.904@tk2msftngp13.phx.gbl...
> Hi
>
> I've a little problem to understand what DrvConvertDevMode,
> DrvDocumentPropertySheets and DrvDevicePropertySheets have to do.
> So lets start with the question about DrvConvertDevMode. If you get the
> parameter CDM_DRIVER_DEFAULT, what does this mean? You have to return the
> default values. Are the default values the "manufacturer default values",
> so fixed values, that I can specify, or is this the values, that someone
> set, by configuring the printer? (so the default settings for this
> machine, the all users settings?).
> Next question, about DrvDocumentPropertySheets... what's the "internal
> DEVMODE structure" ? Is this the default structure for this user? Or for
> the calling application? Or are this just the current settings for the
> current process? Do I have to store them somewhere? Why?
> And a more general question... who is responsible for storing the
> systemwide default settings? Is this my driver? Is the "internal DEVMODE
> structure" what represents those settings?
> And the last question: I always thought, that this is the way it has to
> go: 1) the application sets the current DEVMODEW structure by calling
> DrvDocumentPropertySheets with DM_IN_BUFFER 2) the application lets the
> driver to show the propertypages by calling DrvDocumentPropertySheets with
> other parameters and 3) the application reads the changed DEVMODEW
> structure by calling DrvDocumentPropertySheets with DM_OUT_BUFFER ... but
> then I saw the line 855 in docprop.c (msplot sample of the ddk 3790) ->
> pPI->pPlotDMOut = (PPLOTDEVMODE)pDPHdr->pdmOut; ... it stores a pdmOut
> Pointer... and when applying changes, it directly stores the data into
> this buffer... but I never saw this documented... can someone explain me
> how this works?
>
>
>
> thanks a lot
>
> MR - Rudolf Meier
>
>