Ok, I lied lol.
I’m starting to confuse myself also. Give me a second and i’ll post a screenshot that’ll help explain I hope. I haven’t looked at the calibration stuff in a while so it’s easier to get confused heh.
Edit:
Ok, here you go. So actually, the 0 - 1 isn’t the mesh/bounding box. In the screenshot I put the 0 - 1 coordinates, followed by the application/fullscreen coordinates. The box you see would be where the projection lines up on the table allowing the four corners to be visible so they can be pressed. The whole image is atcually what would be projected; the black is not a background for the image, but the application at fullscreen.
You can see when a blob is near 0 on the x-axis, it is actually 0 + ‘the offset of the bounding box’ so around 184px. So basically if you calibrate and your mesh doesn’t start at 0, you won’t be sending blobs to 0 through TUIO ever. What would appear to be all the way left for a person on their table, would actually be how much the mesh is offset; in my case, about 180px. Sometimes, the projection/mesh may hit the table exactly and then there would be a true ‘0’ coordinate sent.
,
Let me know if that helps at all. I can post the code if you want.
Also, you can test with any of the flash demos on the svn, or even the ones from my blog. It’ll give you a good idea of what’s happening.
