going back in multistack about simple-stack HOT 3 CLOSED

Thank you so much!

from simple-stack.

My question is: is there a way to do that in a simple way different from setting stack history explicitly?

I think you're most likely looking for HistoryBuilder.removeUntil() (which keeps the key you specified, but removes all elements from top to that element), but you will need to set the stack history explicitly with setHistory(newHistory, Direction.BACKWARD).

So something like,

backstack.setHistory(HistoryBuilder.from(backstack)
                                   .removeUntil(KeyToGoTo.create())
                                   .build(), 
                     Direction.BACKWARD);

is there any simple way to push some parameters when going back in stack? I want to have behaviour like "onActivityResult".

Now that's a bit tricky because there are two ways:

1.) either replace the key in the stack with a version of it that has the parameter set, for example you could add a StateBundle to the key (although you should most likely extend it so that hashCode()/equals() does not make it think it is a different object, so equals if obj == this || (obj != null && obj instanceof StateBundle) - that way, using backstack.goTo() would work)

2.) create a "MessageQueue" that you check for pending messages when your view is ready, and identify if the given view has received messages from other views

As you can see, my example used the second option, although it's a bit rudimentary.

from simple-stack.

I know it's probably irrelevant at this point, but with the revised Backstack (which was "BackstackManager" previously after 1.1.0) implementation, I could update the Multistack sample like so:

https://github.com/Zhuinden/simple-stack/blob/f28fcae66287dbb92faefdc905cd2901dd3e7e8d/simple-stack-example-multistack-view/src/main/java/com/zhuinden/simplestackdemomultistack/core/navigation/Multistack.kt

Which is much more convenient to use than BackstackDelegate + setPersistenceTag.

Although it wouldn't change the above recommendation regarding a MessageQueue-like thing. Lately, you'd probably use a shared ScopedService and an EventEmitter.

from simple-stack.