You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to detect if component A's position is within component B when pan gesture (drag) on A is released. However, the position from onPanResponderRelease's gesture.moveY is measured with respect to the entire screen, whereas the position returned from A's onLayoutis measured with respect to the parent view. So i'd need to know the parent view's current height to reconcile the differences.
Expected Behavior
There should be a function to return the position with respect to the entire screen.
Actual Behavior
see above
Reproducible Demo
see above
The text was updated successfully, but these errors were encountered:
Thanks for opening the issue! As it happens, we're using GitHub to track bugs in React Native. If you'd like to submit this as a feature request, please go ahead and create an entry on Canny. It has a voting system and if the feature gets a good amount of votes, it will have a greater chance of being implemented by the community. Closing this now, thanks for understanding!
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
react-native -v
:react-native-cli: 2.0.1
react-native: 0.45.1
node -v
: v6.11.0npm -v
: 3.10.10Then, specify:
Steps to Reproduce
(Write your steps here:)
I need to detect if component A's position is within component B when pan gesture (drag) on A is released. However, the position from
onPanResponderRelease
'sgesture.moveY
is measured with respect to the entire screen, whereas the position returned from A'sonLayout
is measured with respect to the parent view. So i'd need to know the parent view's current height to reconcile the differences.Expected Behavior
There should be a function to return the position with respect to the entire screen.
Actual Behavior
see above
Reproducible Demo
see above
The text was updated successfully, but these errors were encountered: