-
Notifications
You must be signed in to change notification settings - Fork 149
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
Consider using the new AndroidView in 1.4.0-rc01 #285
Comments
This has been already fixed in #377 |
This issue is not fixed. From the javadoc:
The current implementation looks like this which isn't specifying an onReset implementation (v3.0.0):
Currently, if the GoogleMap composable is placed in a LazyColumn, the mapView is re-created/disposed for every item while scrolling. This is very important for our app because it shows multiple maps in a scrollable column. Meanwhile we're stuck with RecyclerView. |
More info is documented in: https://developer.android.com/jetpack/compose/migrate/interoperability-apis/views-in-compose#androidview_in_lazy_lists Basically you'll need to update the implementation to provide a non-null |
🎉 This issue has been resolved in version 6.1.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Is your feature request related to a problem? Please describe.
The new
AndroidView
introduced in 1.4.0-rc01 is optimized to reuse the underlying View when used within a lazy list. Maps Compose usage within lazy lists (LazyColumn, LazyRow, Pager, etc.) could see some performance gains with this new change.Describe the solution you'd like
Try/test out the new
AndroidView
overload but wait to release once 1.4.0 is stable.Describe alternatives you've considered
Do nothing.
Additional context
https://developer.android.com/jetpack/androidx/releases/compose-ui#1.4.0-rc01
The text was updated successfully, but these errors were encountered: