Re: Printing a Bitmap (Win32lib)
- Posted by Euman <euman at bellsouth.net> Jun 16, 2001
- 396 views
DC here's the Constants RASTERCAPS = 38, RC_BANDING = 2, RC_BITBLT = 1, RC_BITMAP64 = 8, RC_DI_BITMAP = 128, RC_DIBTODEV = 512, RC_FLOODFILL = 4096, RC_GDI20_OUTPUT = 16, RC_PALETTE = 256, RC_SCALING = 4, RC_STRETCHBLT = 2048, RC_STRETCHDIB = 8192, RC_DEVBITS = #8000, RC_OP_DX_OUTPUT = #4000, Euman euman at bellsouth.net ----- Original Message ----- From: "David Cuny" <dcuny at LANSET.COM> To: "EUforum" <EUforum at topica.com> Sent: Saturday, June 16, 2001 16:50 Subject: Re: Printing a Bitmap (Win32lib) > > > Bernie Ryan wrote: > > > David C. what about device context? Don't you have > > to set the printer DC to do this ? > > Off the top of my head, I thought the getPrinter stuff was supposed to do > that. I'm only guessing that the problem is that the printer doesn't support > BitBlt, but because none of the other operations failed, it's a likely > candidate. > > As Euman pointed out, you can test this by calling GetDeviceCaps. I'd have > tested it, but I don't have the constants RC_BITBLT handy. > > If it turns out that this is why the BitBlt fails (and at this point, it's > just a conjecture), it would make sense to add the GetDeviceCaps test to > BitBlt in the case of Printer, and fall through to David's code if it's not > supported. > > -- David Cuny > > > >