🚀 go-pugleaf

"Remy Lebeau \(TeamB\)" <no.spam@no.spam.com> wrote:
>
>> It is my current understanding that one must first set the
>> PrinterIndex before one calls SetPrinter.
>
> Then your understanding has been misled.

From a post by Damon:

    if( PageSetupDlg(&psd) )
      {
          HANDLE HMem;
          char device[MAX_PATH], driver[MAX_PATH], port[MAX_PATH];

          Printer()->GetPrinter(device, driver, port, (int)HMem);
          Printer()->SetPrinter(device, driver, port, (int)psd.hDevMode);

          // do some printing...

          GlobalFree(HMem);
          GlobalFree(psd.hDevNames);
      }

and that wasn't working until I added setting the PrinterIndex.

> TPrinter::SetPrinter() assigns the PrinterIndex (amongst
> other things) based on the structures that are passed to
> it.

Thanks. It's working fine now and the TDialogs respect the
currently selected printer even if an API dialog selected it
but I'm still working on getting the API dialogs to respect
it (they open with the default printer).

>> [...] but I just found this in the docs for PRINTDLGEX:
>
> The VCL dialogs do not use PRINTDLGEX.

True, but they do use DEVNAMES.

>> Obviousely there's an error there
>
> There is not.

The docs for DEVNAMES wDeviceOffset says (in part):

    [...] (maximum of 32 bytes including the null) [...]
    This string must be identical to the dmDeviceName member
    of the DEVMODE structure.

However, not only does PRINTDLGEX contradict that, so does
PAGESETUPDLG:

    If both hDevNames and hDevMode have valid handles and the
    printer name specified by the wDeviceOffset member of the
    DEVNAMES structure is not the same as the name specified
    by the dmDeviceName member of the DEVMODE structure, the
    system uses the name specified by wDeviceOffset by default.

They can't both be correct (unless there are different rules
for input and output) but that's a moot point now. It just
added to the confusion.

>> Don't I need to dispose of the TPrinter's current DEVMODE?
>
> No. That is handled automatically inside of TPrinter::SetPrinter().

Good to know.

Thanks.

~ JD