-
-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access locations of gesture touches #221
Comments
Hi, @cwhenderson20 |
+1 for this feature, but for a different use case. I'm having trouble combining Pinch and 2 finger Pan handlers (read the docs, tried the demo, still having issues). With some of this raw data it should be possible for me to use the PanGestureHandler to account for both pan and pinch. |
Are there any solutions to this? Possible using two pan gesture handlers? I tried but could not figure it out #1602 |
Hi! I believe that touch events introduced in Gesture Handler 2 are fulfilling the use case you have described so I'll close the issue. |
Oh thank you I will try that! |
Thanks for the great library!
I'm looking to create a system in which one gesture handler (rotation/pinch) might apply its effects to one of a few different animated views nested within it. In order to figure out which layer to affect, I'll need to access the locations of the individual touches that comprise the gesture. Unfortunately, the focalX/Y and anchorX/Y don't provide enough info for my purposes.
PanResponder from React Native exposes this feature natively, but I'd much prefer to use this declarative library.
It might look something like this:
But ultimately, the format isn't important — as long as it's possible to access the location (and maybe other properties) of each touch on both the state change and handler events.
The text was updated successfully, but these errors were encountered: