-
Notifications
You must be signed in to change notification settings - Fork 156
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
Maintaining Screen State on Backstack? #200
Comments
@rjrjr ? |
@ScottPierce my recommendation is to throw Mortar ViewPresenters out and use Flow's KeyManager exclusively. |
@Zhuinden My team has screens within screens sometimes, which is why we added in Mortar to our Flow usage. I'm assuming that |
KeyManager allows you to put any state into the history entry. It just associates history entries with keys. Personally when I had multiple views that could persist state, my root view delegated the "state persistence callback" to the ones inside itself. A bit manual, but it worked. |
@Zhuinden thanks for the recommendation. I'll look into it and close this if it works. I'm actually not seeing any documentation for it anywhere in the flow repo. Do you know of where I could see an example of it working? |
I think the key manager's state is exposed via |
We're using flow and mortar, and looking to save some data on a screen that when we come back to it on the backstack can be used to restore some state.
How would you recommend we do this?
The text was updated successfully, but these errors were encountered: