Ignacy Łątka

`previousTimestamp` is an `integer`, while `timestamp` was a `float`. This caused around 1ms of disparity, giving an error of roughly 4% per frame. After running with this fix for around...

Hot-reloads break this feature. Looks like both the old `loopAnimationFrame()` and `useFrameCallback()` keep on running after hot-reload.

This component does not have the earlier mention hot-reload issues when running as a component imported from `react-native-reanimated`.

Do we push this component just as an example for now, or should we make a standalone component out of it?

Thank you for the review @szydlovsky :) I've applied most of these changes locally, but while at that, i found some new issues which i will have to resolve before...

Current performance, now that i think of it i will make it much thinner and more transparent. https://github.com/software-mansion/react-native-reanimated/assets/74246391/5e1b5a8f-a3ab-4fc7-82d4-a92774e1095c

https://github.com/software-mansion/react-native-reanimated/assets/74246391/5f22feec-65c4-45a0-b233-bc5ba23c57bb

Hello, we took a look at this issue and it looks `NativeViewGestureHandler` component which wraps the `FlatList` is unnecessary, and is the reason for this crash. Removing it should fix...

Hi @yinminqian, thank you for your report. ~~It looks like the issue lies in lack of optimisation to the Gesture Handler's `FlatList` as compared to React Native's one. As far...

Hi @yinminqian. After some more testing and some discussion with the team I'm inclined to believe the issue you're describing is not related to any of our tools or libraries....