0

my Compose app is structured with a Scaffold with its NavHost and BottomNavBar. The scaffold contains three navigation graphs, each of them containing several composables. Navigation can be achieved by clicking on the bottomNavBar items. The thing is that, from different screens, it is needed to navigate to another composable screen that does not belong to any of the scaffold destinations (graphs), and therefore, has to be shown occupying the whole screen. How would you handle it?

  • How many navControllers? Different navControllers for each graph? And for the "not-scaffold-belong" screen?
  • Where should I place the not-scaffold-belong screen? Should I create a first NavHost containing the not-scaffold composable and the Scaffold with its own navHost?
  • Or should I just handle visibility of bottomNavBar for when the not-scaffold composable is visible?

Thanks!

Improve this question
Related questions
4056
Proper use cases for Android UserManager.isUserAGoat()?
4374
How can I close/hide the Android soft keyboard programmatically?
3568
Why is the Android emulator so slow? How can we speed up the Android emulator?
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.