PLEASE THINK THIS OUT was not telling you. It was begging you. I needed an answer because I am under a deadline. As I stated before I waited for months for this to be implemented. If you're too busy, I understand (we all are), but months back you said you were working on this and were going to implement it using listeners, so I stopped implementing touch based on your statement. I still think virtual methods are an cleared method for the end user. Just like mouseDown, there could be a touchDown, touchSwipe, touchMagnify, etc. based on touch events not mouse events.
I'll give you a reason for not mapping touch events to mouseEvents. Say you had a component that you could drag a selection area over objects to select them. So you click and holding the mouse down while dragging. Now if gestures are mapped to mouse events and you tried a swipe, you would be doing a quick select and not a swipe. They need to be separated. Yes it is a pain, and I am struggling to get it working in a way that works for mice and touches, but I think it needs to be separated this way. iPads, iPhones don't need to resiolve the conflict between a mouse and a touch, but touch screen computers do.
Hopefuly I can get it working in a way that benefits everyone. I can't decide whether to use WM_TOUCH events or WM_GESTURE events. Both have their benefits. And also, my program is cross platform, so touch needs to to work the same on both Windows and Mac. What a pain to implement! That is why I was hoping you would implement it.