How To Use QUERYDIBSUPPORT in Printer Driver

Last reviewed: March 11, 1997
Article ID: Q151892

4.00 WINDOWS 95 kbprg kbprint kbhowto

The information in this article applies to:

Microsoft Windows 95 Device Driver Kit (DDK)

SUMMARY

A printer driver should set flags based on the drivers capability for the DIB when it gets calls to the Control function with the QUERYDIBSUPPORT escape.

MORE INFORMATION

When a printer driver gets call to the Control function with the QUERYDIBSUPPORT Escape, the lpInData parameter points to the BITMAPINFO structure and the lpOutData points to LPINT. Based on the capabilities of the driver, it is expected to set the following flags:

   QDI_SETDIBITS    Device can convert DIB to bitmap
   QDI_GETDIBITS    Device can convert bitmap to DIB
   QDI_DIBTOSCREEN  Device can draw DIB
   QDI_STRETCHDIB   Device can stretch DIB

The driver uses the biBitCount, biCompression, and biPlanes to determine its capability with respect to DIB support. Once the capabilities are determined, it then sets the flags above appropriately. These flags are documented in the Windows SDK in \MSTOOLS\INCLUDE\WINGDI.H.

Additional reference words: QUERYDIBSUPPORT
KBCategory: kbprg kbprint kbhowto
KBSubcategory: DDKPRNT
Keywords : DDKPRNT kbhowto kbprg kbprint
Version : 4.00
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.