Driver Functions SetDIBtoDevice and StretchDIBLast reviewed: February 16, 1995Article ID: Q75946 |
The information in this article applies to:
SUMMARYThe SetDIBtoDevice() and StretchDIB() functions in the PostScript sample driver provided with the Microsoft Windows Device Development Kit (DDK) have ordinal values of 21 and 28, respectively. These functions are documented on page 124 of the "Microsoft Windows Device Driver Kit: Device Driver Adaptation Guide" for Windows 3.1 and on page 5-35 of the "Microsoft Windows Device Development Kit Device Driver Adaptation Guide" for Windows 3.0. When an application calls the SetDIBitsToDevice() function, the Windows graphics device interface (GDI) determines if the driver supports mapping a device-independent bitmap (DIB) to the device by calling the GetDeviceCaps function with the RC_DIBTODEV value. If so, GDI calls the driver using ordinal 21. If not, GDI performs the work to map a DIB to the device. When an application calls the StretchDIBits() function, GDI determines if the driver supports stretching DIBs by calling the GetDeviceCaps() function with the RC_STRETCHDIB value. If so, GDI calls the driver using ordinal 28. If not, GDI performs the work to stretch a DIB. The name of the function the printer driver uses to represent a particular ordinal value does not make any difference. However, we recommend using the original names assigned to these driver functions, SetDIBitsToDevice() and StretchDIBits().
|
Additional reference words: 3.00 3.10 DDK DDKPRINT
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |