The <doc example> for multiple back stacks &amp; bottom navigation causes the bottom icon to highlig...

# compose

[robnik]

The doc example for multiple back stacks & bottom navigation causes the bottom icon to highlight when you are exactly at that destination. Shouldn't it also highlight if your stack is rooted at that destination? In other words, if the bottom nav items are A,B,C,D; and you go from B to E, so your back stack is [B,E], shouldn't the bottom nav show B as selected/highlighted?

[Ian Lake]

Is B a nested graph that contains E? If so, it will continue to appear as highlighted when on E

[robnik]

No, I have only one graph so far. I can get to E through A or B, but I would like to see the highlight, to see what context I'm in. I guess that's not supported currently.

[Ian Lake]

You can write whatever logic you want; it is your code

[Ian Lake]

but the intent is that only when you're on graph B does the item associated with B highlight. If you had a Settings composable that wasn't part of A, B, C, or D that is equally not part of any of those graphs, then A, B, C, or D shouldn't be highlighted

[robnik]

Can I see the full stack from the navController? That doc example shows navController.currentBackStackEntryAsState(). That will point to E if my stack is [B, E]. But how to test to see if B is the root of the current stack?

[robnik]

I'm poking around the API and I don't see it.

[Ian Lake]

No, that's purposefully not part of the API surface

[Ian Lake]

I think if you want your selected item to be 'whatever the last selected item was', I think you'll want to track that yourself in a mutableStateOf and change it whenever an item is selected

[Shakil Karim]

@robnik You can check Chris Tivi app example for the NestedGraph approach.

[robnik]

Thanks. I'll experiment with both of these ways.

[tad]

One of the samples uses backStackEntry.destination.hierarchy to check the selected route. That returns a Sequence of parent destinations in the graph.