UsingMtview

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2011-03-22 08:54:12 →
Size: 1324
Editor: c-174-63-19-15
Comment: Update the instructions to get mtview. The lp page mentioned in the bzr command no longer exists, and couldn't find a direct equivalent lp URL. The git URL provided needed '.git' appended, config step
← Revision 5 as of 2011-03-22 17:58:58 → ⇥
Size: 1843
Editor: c-67-174-110-114
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
== Build == == Install Binary ==
Line 5: Line 5:
Before using, we need to get the code and build it: If you don't need to work with the source code, this is the easiest way to get started with {{{mtview}}} :-) (note that it's currently available only in the Natty archives as a binary install):
{{{
 $ sudo apt-get install mtview
}}}

== Build from Source ==

If you need more than the binary, here's how to get the code and build it:
{{{
 $ bzr branch lp:mtview
}}}
This code is a mirror of a git master branch, maintained by Henrik Rydberg here:
Line 9: Line 20:

Due note, however, that patches, merge proposes, bugs, etc., need to be filed against the LP code!

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

Install Binary

If you don't need to work with the source code, this is the easiest way to get started with mtview Smile :-) (note that it's currently available only in the Natty archives as a binary install): 

 $ sudo apt-get install mtview

Build from Source

If you need more than the binary, here's how to get the code and build it: 

 $ bzr branch lp:mtview

This code is a mirror of a git master branch, maintained by Henrik Rydberg here: 

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

Due note, however, that patches, merge proposes, bugs, etc., need to be filed against the LP code!

Once you have the code, you can build: 

 $ cd mtview
 $ ./autogen.sh
 $ ./configure
 $ 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)