> 2013/9/19 Andrea Franceschini :
> What I don't get now is: is your hardware giving you different session ids to
> every new object that comes in? How would
> you otherwise identify a trace, aka a sequence of touch points > produced by
> the same finger continuously moving on the surface?
I get
2013/9/19 Andrea Franceschini :
> 2013/9/19 Andrea Franceschini :
>> 2013/9/19 Casimiro, Daniel C CIV NUWC NWPT :
>>
>>> I just reread the specification and it looks like duplicate session IDs are
>>> allowed:
>>
>> I'll run some tests and will let you know.
>
> Hi Dan, just ran a quick test and I
2013/9/19 Andrea Franceschini :
> 2013/9/19 Casimiro, Daniel C CIV NUWC NWPT :
>> You could try running my tuiodump utility to get more information.
>
> I'll try with that.
This is the frame I get every second
TUIO Frame 13812:
Added: 748(0.812134,0.707794),
Updated:
Removed: 748(0.
2013/9/19 Casimiro, Daniel C CIV NUWC NWPT :
> I get a new session ID for each and every finger that makes contact with the
> screen. The session ID is constant for a particular finger until I lift if
> off the screen. A new session ID is assigned when that finger is placed back
> on the screen
2013/9/19 Andrea Franceschini :
> 2013/9/19 Casimiro, Daniel C CIV NUWC NWPT :
>
>> I just reread the specification and it looks like duplicate session IDs are
>> allowed:
>
> I'll run some tests and will let you know.
Hi Dan, just ran a quick test and I can confirm I don't get the failed
assert
2013/9/19 Casimiro, Daniel C CIV NUWC NWPT :
> I just reread the specification and it looks like duplicate session IDs are
> allowed:
I'll run some tests and will let you know.
What I don't get now is: is your hardware giving you different session
ids to every new object that comes in? How woul
> > I'm not sure about the spec. I've had this happening using Martin
> > Kaltenbrunner's Java TUIO Simulator, although it doesn't seem to
> > happen with TUIOPad for iOS. This shouldn't be a problem though, it's
> > just that I took a day off and now I don't have access to my actual
> > hardware :
2013/9/17 Andrea Franceschini :
> I'm not sure about the spec. I've had this happening using Martin
> Kaltenbrunner's Java TUIO Simulator, although it doesn't seem to
> happen with TUIOPad for iOS. This shouldn't be a problem though, it's
> just that I took a day off and now I don't have access to
2013/9/17 Casimiro, Daniel C CIV NUWC NWPT :
> This line in tuio_impl::add_touch_point(const tuio::touch_point &tp)?
> Q_ASSERT(!points.contains(touch.id));
Yes, this is the line.
> Is your emitter sending an ADD message with a duplicated TUIO ID? Mine
> doesn't do that. I have to check the sp
> Weird, I didn't have any generic subdir in there. Anyway, I've created one
> and symlinked it there. Now, except for a failed assert in
> qtuiotouch.cpp:190, it seems to work :)
This line in tuio_impl::add_touch_point(const tuio::touch_point &tp)?
Q_ASSERT(!points.contains(touch.id));
Is you
2013/9/17 Casimiro, Daniel C CIV NUWC NWPT :
> I think that plugins are supposed to have the "so" suffix on Mac OS X, but I
> am not sure. I don't have a mac handy right now.
Honestly, I don't know. I just noticed that all the other plugins wer
dylibs so I just went for that. It probably makes s
> I've managed to compile qtuiotouch
> (https://github.com/dancasimiro/qtuiotouch/) on OS X (10.8.4, ftr) using Qt
> 5.1.0 by applying some changes to its CMakeLists.txt file
> (btw, not in Dan's repo yet, you can have a look at it on mine
> https://github.com/Morpheu5/qtuiotouch/ and bear in min
Hi there, I hope you'll excuse me if this message is half-OT, but I
believe its other half is pertinent here :) Anyway.
I've managed to compile qtuiotouch
(https://github.com/dancasimiro/qtuiotouch/) on OS X (10.8.4, ftr)
using Qt 5.1.0 by applying some changes to its CMakeLists.txt file
(btw, not
13 matches
Mail list logo
