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 was archived by the owner on Feb 26, 2023. It is now read-only.
Save instance state between activity destruction/creation is really paintful and generate a lot of boilerplate code. As we do not like this approach because ((lot of code) == (lot of bug)) (and also to save my carpal tunnel), i think we could provide a solution.
Here is a classic way to handle activity instance destruction/creation :
Save instance state between activity destruction/creation is really paintful and generate a lot of boilerplate code. As we do not like this approach because ((lot of code) == (lot of bug)) (and also to save my carpal tunnel), i think we could provide a solution.
Here is a classic way to handle activity instance destruction/creation :
By introducing the
@SaveOnActivityDestroyannotation the written code could be like this :And the generated code like this :