I am perfectly understanding your approach and I am clearly open to simplify
the process of working with multi-touch events in OSG. But can you explain a
little more :

The current approach simulates a moving mouse for the first touch-point,
> so basic manipulators do work, sort of.


I don't really understand it, you also have push, drag and release events
send ? The compatibility with classic manipulators is something important
for us, we don't want to have to make a special manipulator if we use a
multitouch device even if we don't use the multitouch capabilities.

Don't you think that the multitouch handle should be done by a
special GUIEventHandler (something like GUIMultiTouchEventHandler) ? We
should just add the touch ID to the GUIEventAadpter class and move the
TouchData management in this class ?

Cheers,

On Mon, Nov 22, 2010 at 4:20 PM, Stephan Maximilian Huber <
[email protected]> wrote:

> Hi Serge,
>
> Am 22.11.10 14:36, schrieb Serge Lages:
>
> > It's good to see a multitouch support in osgGA, but I was wondering why
> do
> > you need an extra structure (TouchData and TouchPhase) ? Just adding a
> touch
> > ID to the event and using the classic events (PUSH, DRAG, RELEASE) can do
> > the job I think.
> >
> > We're currently working with several touch displays in our company, and
> > that's what we do, we just add a UserData to the event with the touch ID,
> > and all the multitouch handle is done in the application side, it allows
> us
> > to stay compatible with classic mouse events with the same code (we juste
> > set the touch ID to -1) but we never worked on Apple hardware, mostly
> with
> > TUIO enabled hardware or Windows 7 compatible hardware.
>
> This was my first idea, too -- adding an id to GUIEventAdapter and
> adding one GUIEventAdapter per touch-point to the queue. After
> discussing this topic on osg-users, I decided to implement the current
> approach, as it simplify implementing multi-touch on the
> manipulator/application-side, as you don't have to track all
> touch-points and their states by yourself, as all touch-points are
> bundled in one GUIEventAdapter. You can query the GUIEventAdapter for
> the number of touch-points, etc.
>
> I am still open for different approaches -- Robert, what do you think?
>
> cheers
> Stephan
>
>
>
>
>
> _______________________________________________
> osg-submissions mailing list
> [email protected]
>
> http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
>



-- 
Serge Lages
http://www.tharsis-software.com
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org

Reply via email to