 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This section describes the first few steps you should take to create a display driver that is prepared for DirectDraw support.
First, you should consult the DDI for Windows CE Programmer's Guide. You should create a working display driver using the methods described in that document.
Although it is not a requirement, it is suggested that you base your display driver on the GPEC++ base classes. This is the fastest way to get your display driver up and running. It allows your driver to be easily extended with code provided by Microsoft that you would otherwise have to write yourself.
If you do not wish to take advantage of the GPEclasses, please see the DirectDraw Driver Reference.
Note Starting with DXPAK 1.1, you MUST store your DDGPE surface pointer in the dwReserved1field of the DDRAWI_DDRAWSURFACE_GBLstructure to maintain compatibility between GPE and DirectDraw. This is a change from 1.0, where the dwReserved1field of the DDRAWI_DDRAWSURFACE_LCLstructure was used. This change was made to improve the way DirectDraw manipulates its internal data structures during a flip. At the very least, you will need to recompile your driver with the new ddgpe.lib for DXPAK 1.1 or later. You may also need to modify your driver to retrieve its GPE surface pointer from the new location.
Once you have your basic Windows CE GPE-based display driver written and tested, you should continue to the next section.
Last updated on Tuesday, July 13, 2004