After trying to restart the Refresh animation in the MapFragment class after multiple clicks of the Refresh icon, it became clear that the proper way to handle it will require architecture changes. One suggestion I found was to use actors in the backend or ViewModel to maintain state and prevent multiple calls to the Refresh action.
Using the CONFLATED property, we can ensure that the latest call is the only call being processed.
After trying to restart the
Refreshanimation in theMapFragmentclass after multiple clicks of theRefreshicon, it became clear that the proper way to handle it will require architecture changes. One suggestion I found was to useactors in the backend orViewModelto maintain state and prevent multiple calls to theRefreshaction.Using the
CONFLATEDproperty, we can ensure that the latest call is the only call being processed.Helpful Links
actordocumentationactorto reset animationRetroFitandRepositoryusing pre-1.0 Coroutines