bryankeltonadams
10/12/2023, 10:16 PMIan Lake
10/12/2023, 10:31 PMbryankeltonadams
10/12/2023, 10:33 PMIan Lake
10/12/2023, 10:35 PMbryankeltonadams
10/12/2023, 10:41 PMIan Lake
10/12/2023, 10:42 PMnavigate
with a popUpTo
of inventory_graph
vs inventory_list_screen
would differ (assuming what you navigate to is also part of inventory_graph
)popUpTo(inventory_graph) { inclusive = true }
would destroy any state at the inventory_graph
level, while using inclusive = false
or popping to inventory_list_screen
would keep any state attached to the graph around so that your new child screen of that graph could continue to reference itbryankeltonadams
10/12/2023, 10:45 PMIan Lake
10/12/2023, 10:47 PMpopBackStack()
twicebryankeltonadams
10/12/2023, 10:48 PMIan Lake
10/12/2023, 10:50 PMpopBackStack()
on the UI thread (as you have to) and call it back to back (i.e., without any delay
in between or anything silly), then there cannot be a composition happening i between those two callsbryankeltonadams
10/12/2023, 10:51 PMIan Lake
10/12/2023, 10:51 PMfilter
graph and popBackStack("filter", true)
when you want to leave the filter flowbryankeltonadams
10/12/2023, 10:51 PMIan Lake
10/12/2023, 10:51 PMbryankeltonadams
10/12/2023, 10:52 PM