simple-stack: setHistory with force "recreation" even if Key already exists in backstack

I’ve read the tutorial and have browsed other issues, but didn’t find information how to implement such behavior. Or I just missed it.

I need to setHistory() with a certain Key, but it is already in backstack, so now it just behaves like I would call goBack().

I could just override getFragmentTag() by the Key and set an irrelavant value with default value like 0, and when I need to recreated this Key I would set Random.nextInt() just to distinguish the 2 Key’s, but it’s a hack.

Am I missing something and there is some reasonable way to get this behavior?

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 17 (8 by maintainers)

Most upvoted comments

I think we can close the issue, because the main problem I had was handled. And the part about the animation issue, well, I was planing to remove the animation anyway. But still is a strange behavior.

Thank you for such quick response and help!