Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following table describes how the Game API (GAPI) provides solutions for developers who want to write high-performance, real-time games on devices running on Windows Mobile-based devices.
| Goal | GAPI solution |
|---|---|
| Provide fast, animated graphics | Allows direct access to the display's video frame buffer (VFB) memory. Every device is different, so GAPI defines each device. |
| Use the hardware keys on Windows Mobile-based Pocket PCs for game controls | Allows applications to take control of the hardware keys. Defines optimal key maps for each device. |
| Turn off sounds | Turns sound off when the application is in the foreground. |
| Hide the menu bar | Manages hiding the menu bar and restoring it to the proper state when quitting or losing focus. |
| Prevent disruption of the normal use of the device | Manages focus issues. Provides simple calls like IsForeground. |
| Flash the back light for special effects | Manages the problems and provides a simple API call to accomplish this. |
| Use the vibrate alarm as a rumble pack | Future solution under development. |
The following elements are associated with the Game API feature area:
A typical game or application using GAPI calls the following GAPI functions:
- GXOpenDisplay—This function enables GAPI display support.
- GXOpenInput—This function enables normalized hardware key messages.
- GXGetDisplayProperties—This function retrieves a structure that defines the VFB.
- GXGetDefaultKeys—This function retrieves default key values.
GAPI is also useful for other applications that need to use the device in a way that is not supported by the operating system.
Send feedback on this topic to the authors.
© 2005 Microsoft Corporation. All rights reserved.