How to Decide Whether to Use GPE in a Display Driver
The classes for the Graphics Primitive Engine (GPE) provide a code base that you can use to develop a display driver for display hardware. The GPE handles communication within the device driver interface (DDI) layer and handles default drawing. You may be able to use GPE classes to reduce the length of time required to develop and debug a display driver. If you decide not to use the GPE in your display driver, your alternatives include using the software graphics library (SWG) for simple graphics routines and developing a new driver from the beginning.
While Microsoft recommends that you use GPE in most situations, there are some factors that you may want to consider when you choose between a GPE and a non-GPE display driver.
To track your progress in the following table, select the check box next to each step.
| Step | Topic | |
|---|---|---|
| 1. Familiarize yourself with the display driver architecture for Windows CE and with the GPE. | Display Driver Architecture | |
| 2. Familiarize yourself with the benefits and limitations of GPE display drivers. | Benefits and Limitations of GPE Display Drivers | |
| 3. Examine the display driver samples. | Display Driver Samples | |
| 4. Familiarize yourself with GPE classes. | GPE Base Classes | |
| 5. If you decide to use the GPE in the display driver, create a display driver based on GPE classes. | Creating a Display Driver Based on the GPE Classes | |
| 6. Implement functionality that takes advantage of the use of GPE base classes. | User Interface Implementation Considerations |
See Also
Device Driver How-to Topics | Display Drivers | Driver Development Overview | How to Create a Device Driver
Last updated on Tuesday, May 18, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.