UsingMtview

Differences between revisions 2 and 3
Revision 2 as of 2010-09-29 12:55:31
Size: 1371
Editor: c-71-56-223-2
Comment:
Revision 3 as of 2010-10-14 14:16:30
Size: 1466
Editor: c-71-56-223-2
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
mtview is a visual feedback tool that shows touch points, sizes, disconnects, offsets, etc.

mtview is a visual feedback tool that shows touch points, sizes, disconnects, offsets, etc.

Build

Before using, we need to get the code and build it:

 $ bzr branch lp:~utouch-team/utouch/mtview

This code is an import of a git master branch. If, for any reason, branching doesn't work, you can grab the original here:

 $ git clone http://bitmath.org/git/mtview

Once you have the code, you can build:

 $ cd mtview
 $ make

Testing the Device

In order to run mtview, you will need to know the input node for your multitouch device. To find this out, use the instructions here:

Let's say that after running lsinput, you discovered that your MT device input node was /dev/input/event10, then you would run mtview with the following command:

sudo ./bin/mtview /dev/input/event10

At this point, a window will come up and mtview will capture all touch events. Some examples of mtview in action can be found here:

Some known issues with mtview to keep in mind:

  • sometimes the screen starts up with a black background, sometimes with a white one
  • the first touch is not captured
  • around the edges of the screen, touch points are offset; this is a bug, and not (necessarily) a problem with your hardware

Multitouch/Testing/UsingMtview (last edited 2011-03-22 17:58:58 by c-67-174-110-114)