This project has moved and is read-only. For the latest updates, please go here.


Apr 3, 2009 at 10:45 AM
Edited Apr 3, 2009 at 12:05 PM

we posted in a previous post that we always had an error on the service console
now we have an idea what caused it. Once we try to run touchlibprovider in Multitouch.Configuration.WPF, we get the error if we try to run the console again.

We completely rebuilt the solution files, and followed the steps in your how to video very carefully,

everything goes well until we want to execute Multitouch.Configuration.WPF.exe, we get the screen as on your demo, and i also should metion that we have 2 mices connected to the pc, so that when we run console we get 2 red dot's.

but when we click on config device, we can't click anymore, just move the 2 red dots with each mouse seperatly.

Do you have a idea what the problem might be?

and what if we want to use touchlib as an input device, we have a FTIR multi touch sceen and we would like to run the surface SDK on the screen, we were able to install the SDK but not able to control it (not even with mouse drivers).

edit: because we couldn 't click we had to exit the program, but now when we open the service-console.exe again, we have 2 red dot's immediately and no clicking abilities from the start without running WPF.exe

Apr 3, 2009 at 12:07 PM
This is not a problem. It works as it should. You can configure multiple mice provider to block real mouse input (cursor). This is not needed for normal applications that you build using MultiTouchVista. But you have to set this option if you want to use Multitouch features of Windows 7. Otherwise you would not be able to use touch that is "generated" by multiple mice input provider because mouse input has higher priority as touch and touch will be ignored by Windows.

I would suggest that you try TUIO input provider + tbeta.
What do you mean "we would like to run the surface SDK on the screen"?
Apr 3, 2009 at 1:44 PM
ok thank you for your answer.

so how do you do it with t-beta?

first start tbeta let it send TUIO then run the service.console, driver.console and then configuration.wpf?
just a guess, but would this work?

We downloaded the Microsoft surface SDK and we would like to be able to control it trough touch movements on our multi touchscreen
Apr 3, 2009 at 6:39 PM
You have to start tbeta. Make sure it sends TUIO packets. Then start service.console. Using configuration.wpf change to TUIO input provider. Then start driver.console.

How do you think to control Surface SDK using your multitouch screen?
Apr 6, 2009 at 12:36 PM
Edited Apr 6, 2009 at 3:24 PM
We got it working with tbeta, so we can control windows 7 with out FTIR MT screen, thanx a lot for this :p

But, no multitouch, do you know if this is normal, because we would like to let different people control windows on the screen, just like you showed in the driver install demo in paint.

And about surface, we have the SDK installed, and we can control it with just a mouse, but not with a mousedriver.
We don't know yet how to send the tuio blob information to the surface sdk because it doesn't use tuio ofcourse, but with multitouchvista it might work we think.

Edit: it's semi multi touch :P, in firefox we can zoom out by placing 2 fingers and dragging them to each other.
the same for pictures,

But still not in paint...

and for surface we can control it single touch now which is also an improvement.

Apr 6, 2009 at 7:54 PM
Multitouch in Paint works only with Brushes. But pencil is selected by default. You will need to switch to one of the brushes.

Surface reacts to a single touch because it recognizes it as a mouse.