User Tools

Site Tools


faq

This is an old revision of the document!


GestureWorks Visualizer

Overview

The GestureWorks Visualizer is a visualization tool for multi-touch input and gesture analysis. This standalone utility was developed with GestureWorks Core and Unity to display a variety of real-time information, such as raw input data from multi-touch devices, calculated data on touch point clusters, and qualified gesture event output with a simple, intuitive GUI.

The Visualizer interface consists of three windows: the Touch Mode, Cluster Mode, and Gesture Mode.

Touch Mode

The Touch Mode window shows the raw touch data for each individual touch point. Each point is represented with a colored circle with a single ring and a small box containing the following data:

ID: The unique session point identification number.
X: The global position of the touch point on the x-axis
Y: The global position of the touch position on the y-axis.

In the Touch Mode dashboard, a series of fundamental and calculated properties are tabulated:

ID: Unique session identification number.
X and Y: Current global position of the touch point.
Status: Current status of the touch point (ie. Updated, Removed, Added)
Timestamp: Current timestamp for the session.

Below this table is a graph that dynamically shows changes in individual point positions (deltas). Displaying deltas in this way clearly shows trends and patterns in touch point motion and can be used to identify discontinuity in touch point tracking or tracking noise.

Cluster Mode

The Cluster Mode window displays cluster information generated from touch point motion. The cluster data is a combination of results from kinemetric and geometric analysis performed on the clusters.

In this mode there are three possible clusters: one for each of the two GestureWork tiles that appear in the main window, and one for the background. Each new touch point is added to one of these clusters.

When touch points are detected on a cluster, an additional display is over-layed onto the raw touch point data that depicts the size, shape, and center position of the cluster. The change in separation between touch points in a cluster is shown by a ring drawn around the center of the cluster.

In the Cluster Mode dashboard, the fundamental data for each cluster is tabulated:

X: Global position of the cluster’s center on the x-axis.
Y: Global position of the cluster’s center on the y-axis.
Dx: The distance from the cluster’s current center position to its starting position on the x-axis.
Dy: The distance from the cluster’s current center position to its starting position on the y-axis.
Dscale: The difference between the cluster’s current scale and its starting scale.
Width: The current width of the cluster.
Height: The current height of the cluster.
Radius: The radius of the cluster’s point separation.
Points: The current number of points in the cluster.

Below the table is a chart which dynamically displays changes in the point positions.

Gesture Mode

The Gesture Mode window displays data structures after they have been processed by the GestureWorks Core pipeline and collected as gesture events.

When this mode is selected, a GestureWorks tile appears in the window that can be manipulated by the gesture events: drag, rotate, and scale.

The Gesture Mode dashboard displays the current coordinates of the GestureWorks tile and a set of graphs for each of the three gestures. The graphs can be scrolled through using the gesture navigation arrows in the header bar. Each graph displays the real-time data from the gesture event as it is applied to the GestureWorks tile.

Dashboard Controls

The Visualizer dashboard can be minimized and maximized by pressing the bottom button on the dashboard side panel, or moved to the opposite side of the screen by pressing the horizontal arrow button. This allows the entire screen to be available if desired without interference from the dashboard.

What are the differences between GestureWorks 2 and previous versions of GestureWorks?

GestureWorks 2 has significant changes and improvements over the previous versions of GestureWorks. GestureWorks 2 is more efficient, stable, and easier to use. Additional details are on our GestureWorks 2 Changes page.

What hardware do I need in order to create applications with GestureWorks?

You need a computer with Windows 7 or later and some type of input device, preferably a touchscreen. You can give GestureWorks formatted input from a touchscreen or any other type of device.

What software do I need in order to create applications with GestureWorks 2?

Windows 7 or later and a compatible programming language. GestureWorks 2 is a Windows C++ library and comes with bindings for Unity. Samples are provided showing how to use GestureWorks with Unity, Qt Quick, and Win32 C++.

What language is GestureWorks core written in?

GestureWorks leverages the power and efficiency of C++.

What languages does GestureWorks support?

GestureWorks is a C++ library compiled in Visual Studio. Any language which will support binding to a library like this will work. GestureWorks also includes a package for the Unity game engine.

What version of Windows is GestureWorks compatible with?

GestureWorks Core currently works with Windows 7 , 8 and 10.

Does GestureWorks work with Linux or OSX?

GestureWorks Core currently works only with Windows, but Ideum has been developing builds to work on more platforms. Please contact us if you want more details.

Does GestureWorks support Android or iOS?

GestureWorks currently works only with Windows, but Ideum has been developing an Android build. Please contact Ideum if you want more details.

Can GestureWorks Core be used to create commercial software?

Yes, as long as the terms of the license agreement are satisfied.

Can I create my own gestures?

Yes. The GestureWorks processing core is configurable using Gesture Markup Language (GML). This means that you can easily create or modify gestures outside of your application without needing to modify the source code. But GML is for advanced users, most users can use a basic set of default gestures.

How many touch points can GestureWorks process?

GestureWorks imposes no limitation on the number of touch points that can be processed. This is limited only by hardware.

How does GestureWorks receive touch points?

The application passes touch points to GestureWorks every frame.

What do I do If I want to pause event consumption from Gestureworks?

You can stop calling any frame update process, such as processFrame.

faq.1494518734.txt.gz · Last modified: 2019/01/21 16:35 (external edit)