Use gestures in Windows Mobile 6.5

This language reference section describes the touch events, gestures, gesture animations, and other programming elements.

The Touch API consists of two parts: the management of the gesture API of the touch input, and the physical engine API that controls how the display area reacts to the user's touch.

Touch functions, messages, and struct are shared with the mouse, because the application processes a handwritten event like a left-click mouse. For more information, go to the mouse reference page.

Index

Touch gestures introduce window touch and discuss how to implement touch interfaces in your application.

Gesture reference (DTK) API allows your program to monitor and program touch input.

The physical engine overview describes the physical engine and how to use it when implementing the physical excuse.

The physical engine reference (DTK) API controls how the screen responds to touch input and allows your applications to respond to touch as a Shell.

Touch gesture

A touch gesture is described as a short, targeted movement of your finger or pen on a widget or object on the screen. Most gestures are independent clicks. Therefore, they are all equivalent to a finger? Down (WM_LBUTTONDOWN) and finger? Up (WM_LBUTTONUP) pair. The exception is Double Tap, which contains two pairs of transient continuous finger? Down (WM_LBUTTONDOWN) and finger? Up (WM_LBUTTONUP ). Gesture Recognition is based on finger? Down and finger? The up event, coupled with the direction, position, and speed calculated by the gesture reader. Windows Mobile supports the following five gestures.

Gesture Description

TapTap is represented by the Left click of the mouse.

When a finger? Down event and a finger? When an up event occurs within a specified time period and a specific distance, the application receives a separate GID_SELECT gesture message. After the WM_LBUTTONDOWN event, there may be several WM_MOUSEMOVE messages before the GID_SELECT message.

Double TapDouble Tap: Double-click the left mouse button.

When two finger? When an up event occurs within a specified time period and a specific distance, the application receives a GID_DOUBLESELECT message.

The Hold user can press and Hold on the screen to indicate right-clicking the mouse.

The application receives a GID_HOLD message when the Finger remains pressed for more than the specified time and all vertices are within a specific distance. When the finger is lifted or the Hold time reaches the limit, a GID_END message is followed.

The Flick user can move his finger across the screen to start rolling pixel by pixel. If the movement is fast enough, the scrolling continues after the finger is lifted.

The application receives an independent GID_SCROLL gesture message when the finger slide ends. Flick occurs frequently after the Pan (one or more GID_PAN messages followed by a GID_SCROLL message and then a GID_END message ).

You can press your finger on the screen and keep it pressed. Then, you can drag your finger in any direction to show the mouse dragging event.

When the finger position changes, the application receives one or more GID_PAN messages, and then receives a GID_END message when the finger is lifted. A mouse message is an alternative to a gesture message. Panning can occur after the Hold gesture.

Want to know