🚀 go-pugleaf

In my case this won't be a big problem. The printer is exclusively used for
printing these cards, but it would be better if I were to control it.
Here is what I understand I should be trying to do.
1. I need to create a DEVMODE structure in memory.
2. Get the Handle (is this the pointer to the structure?) of the DEVMODE
3. Then the Printer()->GetPrinter() will fill the structure with the current
values.
4. I would then set the specific values as necessary.
5. Then use Printer()->SetPrinter() to apply the new values to the printer.
6. Release the memory used for the DEVMODE

Now I usually use the new operator to create objects in memory so would:

DEVMODE *DeviceMode;
DeviceMode=new DEVMODE;

would this create the structure in memory as you are doing with
GlobalAlloc()

John

"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
news:tvr9tv4cctvuri7np179a37t666i9m1s5u@4ax.com...
> John Scott wrote:
>
> >I wonder if this stuff is necessary. If the printer has the duplex
> >capability and it is enabled then why would I need to use this process to
> >change the setting - it will already be enabled!
>
> Because not every print job needs/wants to print on both sides.
> If duplex were the default, then for instance, invoices (which know
> nothing about duplex, and so won't clear it) would print on both
> sides, and it would be kinda hard to seperate the two invoices.
>
> And, what if the user forgets to set Duplex before printing (or reset
> it after)? If they forget before, they waste cards. If they forget
> after...well....you won't be very well liked.
>
> If you don't manipulate the duplex setting, you do so at your user's
> peril.
>
>