DrvDocumentPropertySheets

Hi

When I get a call to DrvDocumentPropertySheets (PrinterDriver) and the
reason is PROPSHEETUI_REASON_INIT. What do I have to do? ... I have to
create the propertysheet-pages... ok, that's obvious... and do I also have
to copy the pdmIn? (so, can there be a pdmIn?) ... and what about the
pdmOut? ... do I have to store the pdmOut-Pointer to store the data later?
when? When I get another call to DrvDocumentPropertySheet with the
Destroy-Reason? ... or do I have to store this earlier?
Next question... how can I find out, if someone pressed OK and not Cancel?
... MSDN says only, that the value of lParam is not zero, if someone pressed
OK or Cancel... but how can I find out what it was? ...

ok, that's a lot of questions... it's enough if you can answer at least one
:-)

thanks a lot
MR

Carey
Sat Dec 11 18:31:56 CST 2004

"Meier Rudolf" <meiru@gmx.net> wrote:

>Hi
>
>When I get a call to DrvDocumentPropertySheets (PrinterDriver) and the
>reason is PROPSHEETUI_REASON_INIT. What do I have to do? ... I have to
>create the propertysheet-pages... ok, that's obvious... and do I also have
>to copy the pdmIn? (so, can there be a pdmIn?)

No. Create the property sheets and do whatever else you need to do
locally, but that's about it.

>... and what about the
>pdmOut? ... do I have to store the pdmOut-Pointer to store the data later?

No.

>when? When I get another call to DrvDocumentPropertySheet with the
>Destroy-Reason? ... or do I have to store this earlier?

No.

>Next question... how can I find out, if someone pressed OK and not Cancel?
>... MSDN says only, that the value of lParam is not zero, if someone pressed
>OK or Cancel... but how can I find out what it was? ...

Suggest you take a look at the samples in the DDK. Your whole design
should be event-driven and you should avoid trying to save values between
calls.


--
Carey Gregory
Windows Print Drivers & Components
http://www.gw-tech.com

Meier
Sun Dec 12 03:55:46 CST 2004

> Suggest you take a look at the samples in the DDK. Your whole design
> should be event-driven and you should avoid trying to save values between
> calls.

That's what i thought... I always thought, that I have to copy the pdmIn
when I get a call with pPSUIInfo = = NULL and that I get such a call when
it's over, so that I can return the data to pdmOut... but I don't get such
calls... ok, the first one I get, but not the second one... maybe that's
because I work with custom dialogs and I don't handle the WM_NOTIFY
messages... may this be the problem?

MR

Meier
Sun Dec 12 05:13:48 CST 2004

... other question about this.

What do I have to do, that the "apply now" button gets activated, when
someone clicked on something on my custom propertysheet-page ?? What
function do I have to call? ... I think, that's my problem... CPSUI doesn't
remark, that the data changed, since I don't inform it... but I don't know
how...

thanks
MR

Meier
Mon Dec 13 08:54:39 CST 2004

>>When I get a call to DrvDocumentPropertySheets (PrinterDriver) and the
>>reason is PROPSHEETUI_REASON_INIT. What do I have to do? ... I have to
>>create the propertysheet-pages... ok, that's obvious... and do I also have
>>to copy the pdmIn? (so, can there be a pdmIn?)
>
> No. Create the property sheets and do whatever else you need to do
> locally, but that's about it.
>
>>... and what about the
>>pdmOut? ... do I have to store the pdmOut-Pointer to store the data later?
>
> No.

the sample stores the pdmOut pointer...

>>when? When I get another call to DrvDocumentPropertySheet with the
>>Destroy-Reason? ... or do I have to store this earlier?
>
> No.

well... the sample writes to pdmOut, when it gets a call in it's
dialogproc... so, I don't think you're right

>>Next question... how can I find out, if someone pressed OK and not Cancel?
>>... MSDN says only, that the value of lParam is not zero, if someone
>>pressed
>>OK or Cancel... but how can I find out what it was? ...
>
> Suggest you take a look at the samples in the DDK. Your whole design
> should be event-driven and you should avoid trying to save values between
> calls.

it is still event driven...

well... I'll try