-
Notifications
You must be signed in to change notification settings - Fork 132
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
lenghty FlatList (ListView) colliding with the motion animation #17
Comments
Hey David 👋 Not sure if I understand the problem 🤔 FlatList has got some performance improvements so it doesn't render everything in once (as ListView did). Is that what you think? |
Sorry if I was not clear enough. The issue is that even though all 24 items are available on the state, they are not rendered all even if I scroll to the very bottom of the list. The onMoveToDestinationWillStart seems to somehow stop the flat list from rendering all items. If I reach the bottom of the list, the remaining items are not rendered. The issue remains the same even if I replace the FlatList with the ListView. |
Why is the |
It gets fired only once , ie. when navigating from the main list to detail. In fact, the issue is easily reproducible. Just make sure the data file returns more than 20 rows for the FlatList inside the Screens/Detail/Detail.js and you will probably not be able to see all list items even with scrolling. The issue is gone once the animation-making wrapper is commented out:
|
Hi. Your example works fine, but there is an issue when rendering the list rows. I´ve supplied a list of 24 items. But they are not rendered all. Sometimes only the first 9 items are rendered, other times only the first 20 items are rendered. The number is different. But never did I succeed in rendering all 24 items. I´ve found out that all the items (24) are available on the state but they are rendered up to the point when the onMoveToDestinationWillStart will fire as is apparent from the attachment. After this life-cycle fires, no more items get rendered. Is it, somehow, expected behavior?
The text was updated successfully, but these errors were encountered: