🚀 go-pugleaf

JD has reminded me of the solution:

    char Device[ 256 ] = { 0 };
    char Driver[ 256 ] = { 0 };
    char Port[ 256 ] = { 0 };
    THandle hDeviceMode;

    Printer()->PrinterIndex = pIndex;
    Printer()->GetPrinter( Device, Driver, Port, hDeviceMode );

Thanx.


"Alan Bellingham" <alanb@episys.com> wrote in message
news:qgq8hv4fn52ds00n5hv0602s8hfm6lksbv@4ax.com...
> "Remy Lebeau \(TeamB\)" <gambit47@yahoo.com> wrote:
>
> >"Anthony" <awhitesell@attbi.com> wrote in message
> >news:3f1460f3$1@newsgroups.borland.com...
> >
> >> my_hdc1, my_hdc2, my_hdc3, my_hdc4 are all same.  Meaning that you
cannot
> >> get the handle of any printer other than the handle to the default
> >printer.
> >> What use is this?  How do you get the handle of a printer other than
the
> >> default?
> >
> >Call the Win32 API CreateIC() function directly.  Check if it is doing
the
> >same thing.  If it is, then there is nothing TPrinter can do about it,
the
> >OS itself is returning the wrong HDC in the first place.  CreateIC() is
the
> >function that is uses to get the HDC for each printer.
>
> And there's a possibility that, though the value is the same, that the
> content isn't.
>
> It wouldn't surprise me to find the HDC being released back to Windows
> when the next printer is indexed, and Windows then generating a new DC
> in the same place for the new handle.
>
> The whole concept of using the Printer object is not one I've tried - my
> printer code is all written using the underlying API, with
> DocumentProperties() and OpenPrinter() and ResetDC() and the like. I
> suspect that the Printer object is fine for simple use (printing
> reports, say), but may be a little limited for advanced usage.
>
> Alan Bellingham
> --
> Me <url:mailto:alanb@episys.com> <url:http://www.doughnut.demon.co.uk/>
> ACCU - C, C++ and Java programming               <url:http://accu.org/>
> The 2004 Discworld Convention                   <url:http://dwcon.org/>