I'm using Touch2TUIO bridge to interface with with windows7, I don't know if anyone out there has any experience with this but I'd love to get your input.

If you've not familiar with Touch2TUIO I'll give a brief description of what it does: Touch2uniTUIO is an exe that targets the uniTUIO window via command-line argument. Touch events are intercepted by windows hook. It seems to use the WM_TOUCH method to access and forward on touch inputs. When you run the command line, there is this message that says mouse hook is installed — which I'm sure you can see in the video below (sorry of the ghetto player).

The problem I'm having is that is it not allowing single inputs. It seems to always have two inputs. The first which seems to always exist is the mouse. The second and third (and so on) are the next inputs which cannot exist alone. The source code for Touch2TUIO is available to edit and recompile, however I have no experience this api. I simply want to hide the cursor/mouse completely— possibly through the WM_MOUSE method? I'm not really sure.

The other Windows7 bridge does seem to work ok though, the transparent window bridge, called the WM_TOUCH bridge.

Watch the video please, and give your input.
Timeline:

script is run(notice mouse hook message),
mouse is over the window(hover state) touch input is applied— but both remain present,
mouse buttons are used to drag demo box around,
next the keyboard and mouse are used to manipulate box.

The video:removed

Touch2TUIO bridge (dm.tzi.de/research/hci/touch2tuio/)
WM_TOUCH bridge (nuigroup.com/forums/viewthread/4087/)

Any and all input is appreciated! Thanks in advance!

Hi and welcome an board

Have a look at this thread and please use the fixet posted by Ben. You can use the extra cursor (mouse input) for development and for testing in the editor. Just be sure that you deactivate it for your compiled exe version. This should solve the problem...

xtuio.com/index.php/developerblog/suppor...limit=6&start=12

Cheers,

Sandor

Thanks for your reply Sandor!

Sounds like this might be the solution for the problem.

I wasn't able to try this out over the holidays, but I just gave it a shot and it's crying error... not exactly sure why? I replaced files with the fixes that Ben posted. Gives me this error:



Any ideas why? Thanks again!

I think that you may have some old scripts creeping around in there. The BBTouchEventManager.cs is from the early uniTUIO releases (before the iPhoneInput Fakery stuff was added) and is subsequently depricated in the new version.

The 'old' scripts work just fine and use a more centralized touch distribution method, so you can still use them if you want that design, but the fixes from the other thread will (as you can see) break the old scripts.

(you can check out a big ramply post I made about the differences between the old and the new here: www.xtuio.com/index.php/developerblog/su...ituio-april-2010#292)

I would say that unless you are really far into development with the 'old' stuff that you should probably just switch over to the new stuff as it is a bit more flexible.

(and in the case that you are actually trying to use the new stuff but have some old scripts crufting up the place, just get rid of those and it should work fine

Cheers!
-B

Thanks for the help. I believe I was using the most recent version of BBTouch, but Sandor said to try those fixes, and I did so but I guess that won't easily solve my problem.

I guess what I'm wondering is if this extra input — namely the cursor/mouse— is a problem whose solution can be found in Unity3D or in the Windows7Bridge that I'm using. I know I could hard code it to ignore input[0] but I'm not sure if that's the best solution.

Anymore help will be much appreciated! I'm also in contact with Marc who developed this bridge, so we'll see what he says. Thanks.

I found the answer by asking on the nuigroup.com

Just comment out the fake/emulate mouse block of code in the BBTouchEventManager script. See link:

nuigroup.com/forums/viewthread/11549/