wm-touch | 易学教程

(How) Can I emulate touch events on Windows?

阅读更多关于 (How) Can I emulate touch events on Windows?

问题 A utility which I wrote in C++ for testing purposes currently uses the SendInput function to emulate user input, i.e. mouse and keyboard events. I'd now like to extend my program such that it's able to emulate touch events, such that I can verify that the tested program handles e.g. WM_TOUCH messages correctly (though that message is deprecated, I'd still like to verify that it's handled correctly). I don't need to be able to send touch events to a specific HWND , just sending them to some X

WM_TOUCH vs WM_POINTER

阅读更多关于 WM_TOUCH vs WM_POINTER

问题 Which one should I use? I'm only using Windows 8.x, so I don't care about the fact that WM_POINTER is not backwards compatible with Windows 7 etc. I also don't care about gestures; only about raw touches. WM_POINTER's only clear advantage seems to be that it unifies touch and mouse input (but that's easy to work around with WM_TOUCH because mouse events can be checked with GetMessageExtraInfo()). Ease of use is also not an issue; I've been using WM_TOUCH already and I'm just wondering if I

Creating a WM_TOUCH message for PostMessage() in C# / .NET

阅读更多关于 Creating a WM_TOUCH message for PostMessage() in C# / .NET

问题 (For background, see Composing a WM_TOUCH message for SendMessage(), Kinect as a multi-touch device which asks basically the same question as mine but whose accepted answer doesn't actually answer the question. The tricky bit isn't filling in TOUCHINPUT structures but making a valid touch input handle.) I would like to simulate the presence of a multi-touch input device in a nasty hackish way, which in outline goes like this: while (true) { choose locations etc. for simulated touches;

WM_TOUCH vs WM_POINTER

阅读更多关于 WM_TOUCH vs WM_POINTER

Which one should I use? I'm only using Windows 8.x, so I don't care about the fact that WM_POINTER is not backwards compatible with Windows 7 etc. I also don't care about gestures; only about raw touches. WM_POINTER's only clear advantage seems to be that it unifies touch and mouse input (but that's easy to work around with WM_TOUCH because mouse events can be checked with GetMessageExtraInfo()). Ease of use is also not an issue; I've been using WM_TOUCH already and I'm just wondering if I should switch to WM_POINTER. My overriding concern is latency and efficiency (game-related application).