-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Performance Issue] Pool Performance on UI FPS on iOS only with victory-native VictoryArea animating. #754
Comments
Optimally, someone would implement support for animating string props in react-native using the native animated driver, I started work on it but not currently putting any time/effort into it, that should allow speeding up lots of animations with the flip of a switch. But in this case, it seems from the gif that the same effect could be achieved using a static chart and a react-native animated view with white background, which starts out covering the entire chart and slides out to the right. This way, it only needs to render the svg once, and then animate the x position of a white rectangle view using native animation and the simplest possible logic; which should be able to achieve 60fps easily, if it is at all possible to get 60fps using react-native with the specific hardware and operating environment in question. |
@msand Thank you. I have already done that as you say to resolve this issue in this case. But not work in some other case. Thank you again. |
Hi @ATShiTou, alternatively, you could create a clipping mask that reveals the chart underneath (so you don't have to animate the paths, just a rectangle that grows to the width of the device (or height, depending on the orientation) |
Thank you for your advice, I will have a try. |
I've done some more work on native animation: #757 |
I made a animated VictoryArea like this:
Watch the UI FPS ,please . The animation is bad. But it is much better on Android.
Anyone can help me? Thank you in advance.
dependencies:
The text was updated successfully, but these errors were encountered: