Hand Motion data lets applications receive hand motion events, an extended form of mouse event that includes chording, translation/rotation/scaling motion and hand source data. Hand Motion events offer rich possibilities like two handed manipulation that are simply impossible with standard mouse/keyboard channels.
Hand Motion uses a different paradigm than Paths or Contacts. Hand Motion(HM) data is not associated with a specific device whereas contacts and paths are associated with a individual device.
See FWHID_HandMotion.h for reference
For a complete open-source application demonstrating use of Hand Select events to grab windows, Hand Motion events to move windows, and Hand Release events to drop windows, see the XWinder directory of this SDK.
The HandMotionTest application (see HandMotionTest.c) shows the very basic use of the Hand Motion SDK to display incoming hand motion events in a simple window. The application will only display updated hand motion when you gesture with bimanual chords or other chords configured in the MyGesture Editor to output hand motion events.
Source code for the Windows XP HID RAW implementation of Hand Motion API is provided under the MPL 1.1/GPL 2.0/LGPL 2.1 open-source tri-license. To rebuild the Hand Motion library (without Contact/Path API), open the fwhand.vcproj file in Microsoft Visual Studio.
- To rebuild the lib/fwhandxp.lib static library, choose the LibWinXP project configuration and build.
- To rebuild the lib/WinHand2Java.dll Java-native bridge library, choose the Java DLL project configuration and build.
- To rebuild HandMotionTest.exe, choose the HandMotionTest debug configuration and build.
Source code for the Windows 98/ME/2000 implementation of the Hand Motion API, and for the Contact/Paths API implementation is only available by purchasing a license from FingerWorks.
The Mac OS X HandMotionTest application shows the very basic use of the Hand Motion SDK to print all incoming hand motion events to console.
If HandMotionTest is built and run from Apple's Xcode IDE, the output will be in the Run pane.
The application will make little sense if the stdout or console window is not visible when the application is run so it is suggested it be run from Xcode.
Each time the File->Test HID menu item is activated, this app. will find FingerWorks HID devices and begin print any hand motion events received. Use File->Stop Test to release connections to the devices. Nothing will happen until you activate the File->Test HID menu!
Source code for the Mac OS X implementation of Hand Motion API and HandMotionTest is provided under the MPL 1.1/GPL 2.0/LGPL 2.1 open-source tri-license. Source code for the Contact/Path tracking portions of the API is only available by purchasing a license from FingerWorks.
To build, must install in sibling directory of the (FingerWorks-modified) Mac OS X "HID Utilities Source". Open "FWHID HandMotion.xcode" with XCode, Panther's new IDE. Note there are two build targets to choose from:
- FWHID_HandMotion builds the lib/libFWHID_HandMotion.a static library that your application should link to when using the SDK.
- HandMotionTest builds/runs the HandMotionTest sample app for printing hand motion events to the console.
For build to succeed, you may need to update HID Utilities header & library paths in Xcode. The build must have valid references to:
- HID_Utilities_External.h ---- HID Utilities external header file (modified by FingerWorks)
- libHIDUtilities.a ---- HID Utilities static-link library (modified by FingerWorks)
Do NOT dynamically link to the libHIDUtilities.dylib distributed from Apple Developer Connection, as it won't include necessary the HIDSetDeviceAddedCallback HID Utilities API addition by FingerWorks.
Previous: Paths Up to FingerWorks Hand Tracking SDK
Generated on Fri Dec 10 10:08:12 2004 for FingerWorks Hand Tracking SDK by
1.3.8