The information in this article applies to:
SUMMARYIn general, a Windows-based application cannot call the Windows display driver directly to perform graphics primitives. This article details the reasons this restriction is in place. MORE INFORMATION
The Windows display driver communicates with the Graphics Device
Interface (GDI) to perform primitive graphics operations. The
parameters of the entry points (or exported functions) in the display
driver are set up according to the standard interface between GDI and
the display driver. The parameters passed by GDI to the display driver
are only meaningful to GDI and to the display driver. A Windows-based
application has no way to obtain these parameters. For example, the
parameter most-commonly passed by GDI to the display driver is a
pointer to a structure called PDEVICE. Memory for this structure is
allocated by GDI, and its contents are specified by the display driver
during the driver's initialization. The pointer to the PDEVICE
structure is private to GDI; furthermore, the structure of PDEVICE
varies among display drivers.
Additional query words: nowinnt win16sdk
Keywords : kbNTOS400 kbDSupport kbSDKWin16 |
Last Reviewed: June 28, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |