Hi everyone,
i have this problem with a nextwindow screen:

stating to the tuio protocol specifications each blob has a unique id associated to it that should remain the same for all the life of the blob, so i assume from when i put my finger on the screen till i remove it. but on this nextwindow screen im not getting this behaviour. I’m using Touchsmart tuio as a bridge between the device driver and an Air client and this is what happen when i have two fingers on the screen:

- i put finger one on the screen, i get a 2dcur with an alive id of 1
- i put another finger on the screen, i get another 2dcur with an alive of 2
- when i lift the first finger (the one with alive 1) instead of receiving an alive list with one id whose value is 2 (the second finger) im getting an alive with id 1

so it seems that the alive id is not persisting for the full life of the blob but rather that alive ids are being swapped between “fixed slots”

in your opinion is this behaviour correct? or more like a bug of the nextwindow api?

regards,

giuliano

No this behavior is not correct. It sounds like it’s a bug of the TUIO bridge, not the nextwindow. Are you able to edit the way tuio messages are bridged?

we spotted the error: it is a bug in the TUIO bridge we were using. we made a simple tracker using the nextwindow api and the ids are coming correctly. we contacted the author to let him know about the bug.

thanks for the reply.

giuliano