-
Notifications
You must be signed in to change notification settings - Fork 515
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
MapPanel buggy interpolation. HELP! #269
Comments
i' have issue when debug . I guess the deltaY reset to 0. Any solution pls |
did you solve it>? |
Nope. Still looking for a solution... |
#121 looks like the same issue, and it's from 2017 |
The problem is that sometimes animatedEvents are fired on init with y=0, instead of y=initialPosition.
which checks the value of the incoming event and will only change |
I logged the coordinates sent by the native code (on this line) and I logged the nativeEvent coordinates received by the react-native code (my previous comment). In successful cases, two events are sent and received, the first sets the InteractableView's center to 0,0, and the second sets the center to the requested initialPosition. The bug occurs when two events are sent, but only one is received on the react-native side. That would be a bug with the react-native bridge. |
You saved my smooth project. Thank you a lot! |
descriptions: wix-incubator#269 (comment)
In MapPanel interpolation inside Animated.View starts in reverse order on restart until you start to drag:
Reproducing:
It may not appear instantly on this example. But if you try 10 restarts, 2-3 of them will be buggy(reverse interpolation) until you start to drag.
Making more complex animations(backgroundColor, Height, SVG paths) may decrease successful restart to 0, meaning that all your interpolations will be reversed.
Using:
Solves the issue. But limits me on making more complex animations (backgroundColor, Height, SVG paths).
"react-native": "0.57.3"
"react-native-interactable": "^0.1.10"
Need your help guys, please!!!
The text was updated successfully, but these errors were encountered: