Maintaining Screen State on Backstack? about mortar HOT 6 OPEN

@rjrjr ?

from mortar.

@ScottPierce my recommendation is to throw Mortar ViewPresenters out and use Flow's KeyManager exclusively.

from mortar.

@Zhuinden My team has screens within screens sometimes, which is why we added in Mortar to our Flow usage. I'm assuming that KeyManagers doesn't allow for that, right?

from mortar.

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.

from mortar.

@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?

from mortar.

I think the key manager's state is exposed via Traversal.getState(Key) in the original Flow.

from mortar.