Add Touch Manager for improved onTouchEvent Handling

[asm09fsu]

Bug Report

After dealing with using the onTouchEvent callback, I propose we design an architecture for having a touch manager to give callbacks that allow developers to know if certain touch events are happening. Currently the following are thought of as important:

• Taps
  • Single Tap
  • Double Tap
• Pinch
  • Pinch Did Start
  • Pinch Moved
  • Pinch Did End
• Pan
  • Pan Did Start
  • Pan Moved
  • Pan Did End

The point of this manager is to allow developers to use their time dealing with these touch events, instead of building logic to figure out when these touch events occur.

[joeljfischer]

Would it make sense to mirror iOS' own gesture and uiresponder architecture
for familiarity?
On Thu, May 19, 2016 at 5:33 PM Alex Muller notifications@github.com
wrote:

Bug Report

After dealing with using the onTouchEvent callback, I propose we design an
architecture for having a touch manager to give callbacks that allow
developers to know if certain touch events are happening. Currently the
following are thought of as important:

• Taps
  • Single Tap
  • Double Tap
• Pinch
  • Pinch Did Start
  • Pinch Moved
  • Pinch Did End
• Pan
  • Pan Did Start
  • Pan Moved
  • Pan Did End

The point of this manager is to allow developers to use their time dealing
with these touch events, instead of building logic to figure out when these
touch events occur.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#402

[asm09fsu]

I considered that, however if we do something similar to how the gesture recognizer's work is there is still a catch all function for the respective gesture (tap, pinch, pan). I tried to think of it by completely extracting out the logic needed to determine what state you are currently in, and make it a bit more clean.

[joeljfischer]

Fixed in #423