-
Notifications
You must be signed in to change notification settings - Fork 24.7k
Sync offset value to native immediately #50941
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
Conversation
This pull request was exported from Phabricator. Differential Revision: D73622302 |
e340dee
to
8b9887d
Compare
Summary: Without doing this, using Animated.event to update a value with an offset causes the value to revert to not having an offset because the native side doesn't even know about the offset if it hasn't been synced. Don't think there's a better place to sync this for the cases where an animation is kicked off entirely from the native side Changelog: [Android][Fixed] - Ensure latest offset value is synced to native Reviewed By: javache Differential Revision: D73622302
This pull request was exported from Phabricator. Differential Revision: D73622302 |
Summary: Pull Request resolved: facebook#50941 Without doing this, using Animated.event to update a value with an offset causes the value to revert to not having an offset because the native side doesn't even know about the offset if it hasn't been synced. Don't think there's a better place to sync this for the cases where an animation is kicked off entirely from the native side Changelog: [Android][Fixed] - Ensure latest offset value is synced to native Reviewed By: javache Differential Revision: D73622302
8b9887d
to
39fa276
Compare
Summary: Without doing this, using Animated.event to update a value with an offset causes the value to revert to not having an offset because the native side doesn't even know about the offset if it hasn't been synced. Don't think there's a better place to sync this for the cases where an animation is kicked off entirely from the native side Changelog: [Android][Fixed] - Ensure latest offset value is synced to native Reviewed By: javache Differential Revision: D73622302
39fa276
to
d44cb9f
Compare
This pull request was exported from Phabricator. Differential Revision: D73622302 |
Summary: Pull Request resolved: facebook#50941 Without doing this, using Animated.event to update a value with an offset causes the value to revert to not having an offset because the native side doesn't even know about the offset if it hasn't been synced. Don't think there's a better place to sync this for the cases where an animation is kicked off entirely from the native side Changelog: [Android][Fixed] - Ensure latest offset value is synced to native Reviewed By: javache Differential Revision: D73622302
360fa6e
to
5cd6399
Compare
Summary: Without doing this, using Animated.event to update a value with an offset causes the value to revert to not having an offset because the native side doesn't even know about the offset if it hasn't been synced. Don't think there's a better place to sync this for the cases where an animation is kicked off entirely from the native side Changelog: [Android][Fixed] - Ensure latest offset value is synced to native Reviewed By: javache Differential Revision: D73622302
Summary: Pull Request resolved: facebook#50941 Without doing this, using Animated.event to update a value with an offset causes the value to revert to not having an offset because the native side doesn't even know about the offset if it hasn't been synced. Don't think there's a better place to sync this for the cases where an animation is kicked off entirely from the native side Changelog: [Android][Fixed] - Ensure latest offset value is synced to native Reviewed By: javache Differential Revision: D73622302
This pull request was exported from Phabricator. Differential Revision: D73622302 |
5cd6399
to
ce42e6c
Compare
This pull request has been merged in 3e3094c. |
This pull request was successfully merged by Martin Booth in 3e3094c When will my fix make it into a release? | How to file a pick request? |
Summary:
Without doing this, using Animated.event to update a value with an offset causes the value to revert to not having an offset because the native side doesn't even know about the offset if it hasn't been synced.
Don't think there's a better place to sync this for the cases where an animation is kicked off entirely from the native side
Changelog: [Android][Fixed] - Ensure latest offset value is synced to native
Reviewed By: javache
Differential Revision: D73622302