gIIEPadEvent Interface Reference

import "g_IIEPad.idl";

List of all members.

Public Member Functions
HRESULT	HandlePadData (int abs_x, int abs_y, int pressure, boolean fTouch, boolean fTap, int buttonState, unsigned long dwTimeStamp, unsigned long dwSequenceNum)

---

Detailed Description

Interface for client handling of pad events. The user-supplied implementation of this I/F will be called every time data is received from the device, if it data reporting is enabled. Note that you should not attempt to operating on the COM object within the context of this thread (e.g. attempt to close the device while processing an event).

See also:

ConnSetEventNotification

ConnGetEventNotification

Definition at line 65 of file g_IIEPad.idl.

---

Member Function Documentation

HRESULT gIIEPadEvent::HandlePadData (  int  abs_x, int  abs_y, int  pressure, boolean  fTouch, boolean  fTap, int  buttonState, unsigned long  dwTimeStamp, unsigned long  dwSequenceNum )

Pad event data is passed into this method, which must be implemented by the client. See also: gIIEPad::ConnGetRanges gIIEPad::ConnGetPhysicalExtents Parameters: abs_x  relative x position [min..max] abs_y  relative y position [min..max] pressure  z-axis position. [min..max] fTap  Some pads support "tap" detection -- those that don't always return FALSE in this field. fTouch  TRUE indicates object in contact with surface buttonState  For pads that include buttons the bits represent the physical buttons -- returns all 0's on pads without buttons. dwTimeStamp  Timestamp for sample. In units that support HW timestamping this will be the time at acquisition within the pad -- otherwise it is stampeed when received by the computer. dwSequenceNum  Circular sequence # generated by the HW. This may be useful for determining packet loss. Note that not all pads support this feature -- in which case it is "emulated" by the implementing software on the host. Note that in many cases this field is actually only 8 bits and will wrap accordingly.

---