Touch Gestures Window AutoGesture (Compact 2013)
3/28/2014
You can enable automatic handling for flick gestures (AutoGesture) in all Win32 windows that allow scrolling by including the Sysgen variable SYSGEN_GESTUREANIMATION in your run-time image. AutoGestures only work with windows that have the WS_HSCROLL and/or WS_VSCROLL styles.
Note
The SYSGEN_GESTUREANIMATION variable replaces the SetWindowAutoGesture function that was used to enable automatic gestures in Windows Embedded CE 6.0 R3. All of the WindowAutoGesture API functions have been removed in Windows Embedded Compact 2013.
If you enable automatic gestures, you do not have to process the WM_GESTURE window message for the scroll message, because the window procedure automatically passes the WM_GESTURE message to the default window procedure. Instead, you process the WM_HSCROLL and the WM_VSCROLL messages. The window automatically processes the flick gesture messages, and generates the horizontal or vertical scroll messages with the physics engine effect applied. For details about the physics engine, see Touch Gestures Physics Engine Reference.
Window AutoGesture does not process the pan gesture. The application must process the pan gesture in order to respond to it. This gives the application the flexibility to determine what the response will be. For example, an application with a multiple-selection list might respond to the pan gesture by dragging a rectangle for multiple selection (requiring neither WM_HSCROLL nor WM_VSCROLL), or by smoothly scrolling the list (equivalent to dragging a finger on the scroll bar).
To add this feature to your OS design, select the catalog item "Gesture Support for Win32 Controls" in Platform Builder, or add SYSGEN_GESTUREANIMATION to your design.
To include the window auto gesture in your design, you must include the sysgen variables SYSGEN_ANIMATEGESTURE, SYSGEN_PHYSICSENGINE, and SYSGEN_TOUCHGESTURE.
Requirements
Header |
winuser.h |
sysgen |
SYSGEN_GESTUREANIMATION |