multi-touch-dev team mailing list archive

[peng zhang <zhang.austin@xxxxxxxxx>]

2011/4/18 Stephen M. Webb <stephen.webb@xxxxxxxxxxxxx>

> On Mon, 2011-04-18 at 12:46 +0800, peng zhang wrote:
>


> > > 4 When will QT integrate geis-like api into its multitouch framework
> and at
> > > that time will the lower dependency
> > > ask for XI2.1 and grail? And will grail supporting within QT be one
> > > plugin-like way to distinguish with QT's
> > > native gesture engine?
> >
> > The idea is that Qt will adopt geis as a "native gesture recognizer,"
> > much like it already does for other systems with native gesture
> > recognizers.  The murky details will be hidden inside Qt and
> > applications will simply compile and run as they do elsewhere.

Thanks for reply. In fact, what I want to know is how QT decide to use the
below gesture recognize if there were more than one gesture recognizer? Say,
if QT uses geis, then also means that we must have grail support inside. But
anyway, it might be only some switch from build-time, and if user decided to
use someone recognizer that means of course they also need all backend
stuffs. Thanks.


>
> > > 5 Is Touchegg using ginn and is touchegg only working with those apps
> which
> > > doesn't support multitouch
> > > originally? Say, if I have a app which capture MT event using QT touch
> > > framework, then it would be possible
> > > to confuse if using touchegg which capture the same event on the app?
> >
> > Touchegg does not use ginn.  Ginn is a standalone daemon application.
> > Touchegg uses the geis API.  José can better describe how it integrates
> > with applications.
>
With a glance look on them, it's more *like* touchegg is one UI of ginn
because touchegg can use those info/method from ginn to do those things it
is described from that meeting minutes.
And both ginn and touchegg mainly target for those app which doesn't support
MT natively?

Thanks again for your answers.