sorry guys I’ve found some little bugs on tuioSimulator, I’m sure most of you won’t notice them as you’re not using the “fseq” message. The bug affects only the /tuio/2Dcur profile. I’m checking sources and will upload here the new version as soon as it’s ready (maybe a couple of hours?? xD) and send it to reactivision guys. The problem is “fseq” messages are not properly sent in /tuio/2Dcur and not “alive” messages are resent periodically as done for /tuio/2Dobj profile.
** for those of you who wanna now why “fseq” is so important:
fseq messages let you know when a “frame” is finished and data from the next frame is being sent. Why this matters? ‘Cause all recognition stuff, movements, etc,.. SHOULD be done when a frame is finished, otherwise you could be using not updated information for a blob or over calculating some things, for example, imagine there are 3 blobs, so 3 “set” messages arrive, if every time a set message arrives you update your screen data you would refresh 3 times for a single “frame data”, and if you are calculating relationship between blobs for example when 1st set message arrives when calculate your stuff you’re using not updated data for the other two blobs! Well, I’ve tried to explain it, but as english is not my mother tongue maybe I just created you more confusion. If there’s someone still doesn’t understand let me know I’ll make an effort to explain it in plainer english.
Here it is what I call the beta2 with fseq problems solved and periodically resend /tuio/2Dcur alive messages as expected from TUIO specs. It *may* have some unexpected values, as an in depth refactoring should be done to threat cursors as objects are threated, however it should still work as all previous versions.
If having problems with this version continue reading and try the last one