WindowsTouch
Author: | u7angel |
Date: | 26 Sep, 2013 |
Category: | plugin |
Credits: | vux / tiny bits by u7angel |
Download
64bit
receive windows touch
Description

Here we go, a plugin to receive touch (multitouch) information from windows7/8 touch compatible devices.
This plugin was tested with various hardware and OS versions:3M,Surface Pro, Dell Touchmonitor, PQLabs Frame, Windows7 and Windows8
Nasty Windows Feature: Normally palmrejection is on by windows default, resulting in no touchdata on towndown. you can turn it off now.
Initially after getting stuck developing this plugin i talked to master vux who got around the problem with a hook, getting control of the renderer. Microsoft didn't make it easy ;)
Comments
Comments are no longer accepted.Please create a new topic in the vvvv beta forum to discuss this contribution.
Sweeeeeeeeeeet!! Waited a long time for this =)
cool!
What good news! Thank you guys!
great! can't wait to try it out.
you could make your plugin inherit from VVVV.Hosting.WindowInputNode which handles all the subclassing thing for quite exactly this reason ;)
vvvv.sdk commit
he woei, the plugin is dynamic. feel free to make changes if you think its an improvement.
if I place two fingers on the renderer and move them around in circles the quads quite often end up swapping or just being in the wrong place. Anyone else seeing this?
thanks
the plugin gives you touchID's. you can sort your touchXY with them. does this work for you ?
hey U7 - seems to be this device I'm trying it on. Another MT device it's working well. I'll do some more testing. great plug thanks. always been working with hid before and it doesn't manage the IDs which was always a pain.
Lovvvvely. Got this working on an ELO dual touch screen in Windows 8. Thanks (as usual) to Vux and the Angel.
On Windows 8 I sometimes get Touch Points which are stuck in the plugin, even if not touching the Screen anymore. It's getting solved by resetting the node. Anyone else experienced this behaviour?
@readme. confirmed with various touch screens. same for touchdata pin from dx11 renderer. we are filtering those ghost points with a small module
interesting, i haven't seen these yet
Has somebody tested it with a touch foil?
should it work or need to follow a different approach?
Thx for the plugin u7angel. Already successfully using it with PQ Labs IR touch frame. Very good and nice work!