Resources | developer.brewmp.com Resources | developer.brewmp.com

Developer

resources

Touchscreen event handling

Along with any application-specific handling that is needed, all touch events should be sent to the root container or root form. In addition, the application can customize widget actions in response to touch events by replacing or augmenting the default touch controllers. See Customizing touch event handling.

The following touch events should be sent to the root container or root form:

  • EVT_POINTER_DOWN is sent when the screen is first touched.
  • EVT_POINTER_MOVE is sent when the first finger or first pointing device is moved across the screen while remaining in contact with the screen.
  • EVT_POINTER_UP is sent when the first finger or first pointing device is lifted up from the screen.
  • EVT_POINTER_STALE_MOVE is sent when the event queue contains additional unprocessed moves for the first finger or first pointing device.
  • EVT_POINTER_MT_DOWN is sent when a multitouch down for any ptrID other than 1 is detected.
  • EVT_POINTER_MT_MOVE is sent when a multitouch move event occurs and ptrID 1 is not in contact with the screen.
  • EVT_POINTER_MT_UP is sent when a multitouch up for any ptrID other than 1 is detected.
  • EVT_POINTER_MT_STALE_MOVE is reported when the event queue contains additional EVT_POINTER_MT_MOVE events.

For all touch events, dwParam contains location information and the number of taps. Helper functions defined in AEEPointerHelpers.h can be used to obtain the name-value pairs from dwParam. For more information, see AEE_POINTER_GET_XY() in the For more information on the API listed below, see the http://developer.brewmp.com/reference/api-all. .