touchUp and touchMoved Issue.

[JugalRupela]

Hi nneonneo, First off all thanks for this wonderful Plugin. I ask for help at openframeworks forum, then someone directed me here...I'm not a pro... but I'm facing some issues here, I wanted to create a simple swipe gesture, so I'm trying different methods to achieve that. (may be you can help me to achieve that?)
Whenever I want to call any function from touchUp or touchMoved, sometimes it just call it as soon I touchdown or sometimes it doesn't call at all... (for example :- I want to print anything on touchMove or sometimes touchUp.... it will just print as soon I touch down).
Like I said I'm just a beginner, appreciate if you can assist me...... Thanks in advance.

[nneonneo]

What device are you using this with, and what version of Windows?

On Tue, Dec 29, 2015, 21:47 Jug notifications@github.com wrote:

Hi nneonneo, First off all thanks for this wonderful Plugin I ask for help
at openframeworks forum, then someone directed me hereI'm not a pro but I'm
facing some issues here, I wanted to create a simple swipe gesture, so I'm
trying different methods to achieve that (may be you can help me to achieve
that?)
Whenever I want to call any function from touchUp or touchMoved, sometimes
it just call it as soon I touchdown or sometimes it doesn't call at all
(for example :- I want to print anything on touchMove or sometimes touchUp
it will just print as soon I touch down)
Like I said I'm just a beginner, appreciate if you can assist me Thanks in
advance

—
Reply to this email directly or view it on GitHub
#1.

[JugalRupela]

I'm using windows 10, with Dell Touch monitor S2240T..

[micuat]

Hi, I don't know if this is related or not, but I found ofApp::touchDown(...) was called several times upon a single touch (id is always the same), and same for ofApp::touchMoved(...). I solved the problem by comparing x,y values in ofApp::touchDown(...) but it will be nice to solve it in the event handler. I feel like this may be an issue with Windows API.

I'm using Surface Pro 2 with Windows 10.

[mccap079]

Win10 with external 3M touch display, can confirm touch events are called twice per touch with matching touch.id.

[griv]

I just hit the double touchDown issue today. Solved it by adding a check to see if the touch.id is already in the touchMap.

if (touchMap.find(touch.id) == touchMap.end()) { touchMap[touch.id] = touch; }

[nneonneo]

@griv do you want to submit a PR to fix it?