See Also
 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. |
A user can interact with a device in several ways. Traditional ways include:
- Button presses
- Stylus input
- Software or hardware keyboard.
Non-traditional input methods include:
- Voice control
- Networked device interactions
- Using the camera as a positional joystick
- GPS position information
All Windows Mobile devices include buttons and a directional pad (d-pad), so these controls are considered the primary input interface for games.
Capturing Button Presses
EveryWindows ®phone has consistent, predefined button assignments, which include Calendar, Messaging, Tasks, and Contacts.
The layout of the buttons, d-pad, and display can be portrait or landscape, and QWERTY keyboards are becoming common.
The way to interact with the hardware buttons on a Windows Mobile 6.5 device is by using these input functions:
-
AllKeysenables your program to obtain key press information.
-
GetAsyncKeyStateprovides information about the state of a
specified key.
Capturing Stylus Input
Many devices running Windows Mobile 6.5 support a touch screen. You can make your game stylus-aware by using the APIs described in the Touchsection.
Capturing Keyboard Input
Most Windows Mobile devices support a keyboard using a hardware–independent keyboard model. The OEM usually determines the keyboard layout for a specified device. See the Keyboardsection for more information about handling keyboard input.