I made a “UI” with a SplitContainer, Panel and a TextBox in it and wrote this code ( adding references to the sample Windows7.Multitouch and assemblies ). I wanted to experiment with those wrappers and see whether it made life easier or more difficult and so I thought I’d quickly replicate what I’d done previously and so I started a new Windows Forms application to see if I could handle WM_TOUCH messages in it. NET world didn’t fill me with joy and so switching to using someone else’s wrapper seemed like a smart move. Wrapping those COM objects might not have been too ugly a job but the initial thought of trying to track down the TLB info for the COM objects involved ( assuming that there is TLB info for those COM objects because it’s a lot less fun if there’s not ) and then try and get it imported into the. Following on from the previous post and the one before, it was fun to play with my own interop wrappers for a while but I figure it’s going to be a lot more productive to use the interop wrappers contained up at Īnd they also include wrappers for the manipulation API and its friend the inertia API which I didn’t really want to get into wrapping if I could avoid it.

Windows 7 multi touch