Re: [Development] Extending touch semantic information and Qt backends

2016-02-12 Thread Ariel Molina
Further investigating i just read: https://www.kernel.org/doc/Documentation/input/multi-touch-protocol.txt Which is a good read about the status of multitouch in the Kernel, moreover it explains the type of objects to be reported which are divided non identifiable and identifiable objects. Moreov

Re: [Development] Extending touch semantic information and Qt backends

2016-02-11 Thread Ariel Molina
Edward, I strongly agree with your analysis. Any generalized touch (marker, finger, pen) has a general elliptic shape defined by a rectangle, when a device does not support that info, touches are just degenerate squares 0 by 0 and zero area. But richer devices might provide blob rect and blob angl

Re: [Development] Extending touch semantic information and Qt backends

2016-02-11 Thread Ariel Molina
On Thu, Feb 11, 2016 at 6:31 AM, Rutledge Shawn < shawn.rutle...@theqtcompany.com> wrote: > > > On 11 Feb 2016, at 11:35, Александр Волков > wrote: > > Angle is not enough, because for compatibility with older apps > TouchPoint::rect() should be as close as possible to the rotated rect. > > See h

Re: [Development] Extending touch semantic information and Qt backends

2016-02-11 Thread Ariel Molina
> > I’m interested. But I will warn you that my attempts to make MouseArea > and Flickable handle touch events directly have run into issues with the > complexity of handling two completely independent event types with > similar-but-different code, backwards compatibility, getting reviews on the >

Re: [Development] Extending touch semantic information and Qt backends

2016-02-11 Thread Ariel Molina
> > >> There is QTouchEvent::device(). Isn't it enough? > > > - Area & rotation. There is TouchPoint::area() and ::pressure() but >> currently there is no support for ::angle(). Angle can be zero when not >> supported. >> > Angle is not enough, because for compatibility with older apps > TouchPoi

Re: [Development] Extending touch semantic information and Qt backends

2016-02-11 Thread Welbourne Edward
Very much a digression but ... > TUIO models the touchpoint as a rotated ellipse though, right? [snip > URL] And I think that’s nice, for finger touchpoints at least > (although markers could be any shape). It can be assumed to be the > ellipse inscribed in a rect Traditional graphics always th

Re: [Development] Extending touch semantic information and Qt backends

2016-02-11 Thread Rutledge Shawn
> On 11 Feb 2016, at 11:35, Александр Волков wrote: > Angle is not enough, because for compatibility with older apps > TouchPoint::rect() should be as close as possible to the rotated rect. > See https://codereview.qt-project.org/#/c/114238/ > In other words it should be a projection of the rota

Re: [Development] Extending touch semantic information and Qt backends

2016-02-11 Thread Rutledge Shawn
> On 11 Feb 2016, at 02:13, Ariel Molina wrote: > > Hi, > > Research is strong on natural user interfaces, and now market is stronger > than ever and growing. I was working on the TUIO QPA and found a couple of > bugs, which I already pushed patches [1] [2] which I hope make it to 5.6.x. >

Re: [Development] Extending touch semantic information and Qt backends

2016-02-11 Thread Александр Волков
Hi, Ariel. 11.02.2016 04:13, Ariel Molina пишет: - Multiple touch devs/layers and Person tagged touches. Can be easily added by extending QWindowSystemInterface::TouchPoint with a device identification, like device(). This will also work for TUIO. There is QTouchEvent::device(). Isn't it enoug

[Development] Extending touch semantic information and Qt backends

2016-02-10 Thread Ariel Molina
Hi, Research is strong on natural user interfaces, and now market is stronger than ever and growing. I was working on the TUIO QPA and found a couple of bugs, which I already pushed patches [1] [2] which I hope make it to 5.6.x. OTOH, to further enhance touch interfaces I want to bring the discus