You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.
In the list with PLANTS, when filter button is pressed emitting of new live data and sorting is executed more than once.
I added logging to be more clear:
In List.applySort:
println("Name: ${plant.name}, position: $positionForItem")
And in
val plants: LiveData<List> = liveData<List> { ...
println("Plant list: ${System.identityHashCode(plantList)}")
And this is observed in Logcat:
Same is observed when the filter is press again, but log is much bigger as all plants are shown.
How can this be optimized?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the list with PLANTS, when filter button is pressed emitting of new live data and sorting is executed more than once.
I added logging to be more clear:
In List.applySort:
println("Name: ${plant.name}, position: $positionForItem")
And in
val plants: LiveData<List> = liveData<List> { ...
println("Plant list: ${System.identityHashCode(plantList)}")
And this is observed in Logcat:
Same is observed when the filter is press again, but log is much bigger as all plants are shown.
How can this be optimized?
The text was updated successfully, but these errors were encountered: