Issue 337 in pymt: Unresolved wm_touch handling in wm_touch.py
py...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 337 by allen.bevans: Unresolved wm_touch handling in wm_touch.py
http://code.google.com/p/pymt/issues/detail?id=337
What steps will reproduce the problem?
1. Use wm_touch as your touch provider on a system with wm_touch recognized
hardware (Windows 7)
2. Interact with an applet for constantly for around 7 to 10 minutes
3. Watch in awe as your app stops responding to wm_touch input, but still
responds to mouse, TUIO, and other input...
What is the expected output? What do you see instead?
Expected - wm_touch input should still be interpreted by the pymt app. It
fails after 65535 discrete touch messages from Window's GetTouchInputInfo().
What version of the product are you using? On what operating system?
pymt 0.4 on Windows 7 64, with the 3M M2256PW as an input device. This will
also be an issue with pymt 0.5 as well, and is most likely an issue with
all wm_touch hardware.
Please provide any additional information below.
Here's the fix:
After calling GetTouchInputInfo() (line 177 in pymt 0.5),
CloseTouchInputHandle(wintypes.HANDLE(lParam)) needs to be called -
otherwise wm_touch grabs touch handles from the OS without releasing them,
which maxes out at 65535 touches msg's (as handeled by _touch_wndProc)
py...@googlecode.com
Status: Started
Comment #1 on issue 337 by txprog: Unresolved wm_touch handling in
wm_touch.py
http://code.google.com/p/pymt/issues/detail?id=337
that's a very funny bug. Thanks for reporting !