Hello and thank you for this great package , What I'm trying to achieve is to be able to detect the last pageStack element so I can prevent the app from exiting once all screens are popped using android back button , what I did in the willPopScope : onWillPop: () { if (myPageStack.peek() == 0) return Future.value(false); return Future.value(true); }, This has 2 downsides , if somehow the last element isn't the initialPage(==0) a no element error raises and the app becomes no longer usable. If the last element is indeed the initialPage which is 0 then pressing the back button does nothing meaning if there are screens pushed (nested) into that initialPage they won't pop being unable to reach previous screens in that last pageStack. My question is , is there a way to simply find out whether the pageStack is pop-able or not like the (maybePop) function in order to know that the current screen is actually the last so we can anticipate the app from going into background ? Thank you looking forward to your input !

As of now, I couldn't find any way to do this directly from scaffold. I'll try doing it with Stack and all but I'd like to know if there is an easier way to do so.

Is it possible to have an overlay widget appear with bottom navigation button press?

With my current implementation when I press a bottom navigation button, it will always present a new blank screen and place widgets on top of that, here is what Ive tried doing:

    return BottomNavLayout(
      // The app's destinations
      pages: [
                  (...)
                   (navKey5) => BottomNavigationMoreButton()
                 ]

class BottomNavigationMoreButton extends StatefulWidget {
  const BottomNavigationMoreButton({Key? key}) : super(key: key);

  @override
  _BottomNavigationMoreButtonState createState() => _BottomNavigationMoreButtonState();
}

class _BottomNavigationMoreButtonState extends State<BottomNavigationMoreButton> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      backgroundColor: Colors.transparent,
      body: SizedBox.expand(
        child: DraggableScrollableSheet(
          key: UniqueKey(),
          minChildSize: 0.0,
          builder: (BuildContext context, ScrollController scrollController) {
            return Container(
              color: Colors.blue[100],
              child: ListView.builder(
                controller: scrollController,
                itemCount: 25,
                itemBuilder: (BuildContext context, int index) {
                  return ListTile(title: Text('Item $index'));
                },
              ),
            );
          },
        ),
      ),
    );
  }
}

The idea here being that a DraggableScrollableScreen would appear over whatever content you are already looking at when you press one of the bottom navigation icons.

Possible?

Excellent plugin, and my apologies if this is a general Flutter inquiry not related to this package specifically.

I want to have a page which can be pushed from anywhere in the app. The page is a full-screen pop-up dialog, and I do not want the bottom bar to appear on this page. However, I want the user to be able to pop from the dialog back to the position they were at (tab selected, page, etc.)

I am using RootNavigator = true within my Navigator.push to accomplish this. However, when I use push a page from the root context, all my previous routes (the entirety of bottom_nav_layout routes) are immediately disposed.

This became an even more apparent issue with a video plugin which uses rootNavigator for full-screen. Opening a video in full screen from the root context (to hide the bottombar) disposes the entirety of the bottom bar all together. Thus, when the user exits full screen, the app goes back to the very home of bottomNavLayout, not the video page they were at.

As a temporary solution for the above, I had fullscreen open without root navigator, and hid the bottomBar using a changeNotifier. Still not the best solution.

I want to be able to push a page directly on top of the entire navigation stack - independent of the bottombar - and return later with the navigator preserved.

Thank you for your time.

Id like to have the bar scroll away as the user scrolls the screen (something like this: https://pub.dev/packages/scroll_bottom_navigation_bar)

To do this I believe I need to program some animation with a scrollcontroller.

Is there anyway to attach a scrollcontroller to your bar?

PS. Bar is working outstanding!

First off all, the package looks great so far.

One key requirement some (myself included) may have: Persistent bar.

We want our bottom navigation bar to always show, no matter what page is navigated to. currently, a new page will cover the bottom navigation bar.

Can it somehow optionally be programmed to maintain the bottom nav bar at all times?

First of all thank you very much for this brilliant package!

Now my question: How can I programmatically select a screen? Example: Tab1 (ArticleScreen) is active. When I receive a push message, I want to go to Tab4 (FormationenScreen). Is this possible? Previously I have used named routes and get there. But with tabs I do not know the solution.

:
  return BottomNavLayout(
    pages: [
      (navKey) => NavigatorWithoutRouteNames(
            navKey: navKey,
            initialPage: ArticleScreen(animationController: animationController),
          ),
      (navKey) => NavigatorWithoutRouteNames(
            navKey: navKey,
            initialPage: StageScreen(animationController: animationController),
          ),
      (navKey) => NavigatorWithoutRouteNames(
            navKey: navKey,
            initialPage: GuuggemusigScreen(animationController: animationController),
          ),
      (navKey) => NavigatorWithoutRouteNames(
            navKey: navKey,
            initialPage: FormationenScreen(animationController: animationController),
          ),
      // (navKey) => ArticleScreen(animationController: animationController),
    ],
    bottomNavigationBar: (int currentIndex, Function(int) onTap) => SalomonBottomBar(
      currentIndex: currentIndex,
      onTap: (int index) {
        animationController.reverse().then<dynamic>((data) {
          onTap(index);
          animationController.forward();
        });
      },
      margin: const EdgeInsets.only(left: 8.0, right: 8.0, top: 16.0, bottom: 20.0),
      items: [
        SalomonBottomBarItem(icon: const Icon(LineIcons.bullhorn), title: const Text('News'), selectedColor: AppTheme.bluevereinigte),
        SalomonBottomBarItem(icon: const Icon(LineIcons.music), title: const Text('Guuggerbühnen'), selectedColor: AppTheme.bluevereinigte),
        SalomonBottomBarItem(icon: const Icon(LineIcons.drum), title: const Text('Guuggemusigen'), selectedColor: AppTheme.bluevereinigte),
        SalomonBottomBarItem(icon: const Icon(LineIcons.users), title: const Text('Formationen'), selectedColor: AppTheme.bluevereinigte),
      ],
    ),
    // If savePageState is false, pages cannot be transitioned out.
    savePageState: true,
  );
:

Hi!

To begin with, I will say that this is an excellent solution that is perfectly adapted to any concept. Just love it.

Question: Is it possible to hide nav bar on a certain screen? (Ex: When user logOut from account and gets to the intro screen.) Thanks.

How do you navigate to a page without a nav bar. From a screen/widget which has nav bar. Is this possible?

When I try to open a new screen it always open in the nav bar.

callback to customize action when there's one page on stack

bottom_nav_layout: #^3.0.9
    git:
      url: https://github.com/nowjordanhappy/bottom_nav_layout/
      ref: new-feature-willpop

I want change the current bottom navigation bar to another. Like: When I click on add to cart button from product detail page it should show selected bottom navigation bar to cart page. Currently It shows me the page but selected page is still homepage.

Also I can't handle navigation from button on the pages to change bottom navigation.

Hello , I'm back here after being stuck with an issue for a while , the problem im facing is that using willPopScope on top of the BottomNavLayout in order to control what happens when the android back button is pressed , makes it impossible of taking advantage of willPopScope again in the nested screens locally , I'm having few scenarios where I need to dismiss a sheet or an overlay on back btn press but instead the global willPopScope gets triggered and the local screen's one doesn't ! I noticed that if I hot reload (global willPopScope get's rebuilt) the local willPopScope starts triggering but the drawback is that the BottomNavLayout breaks completely with a "Bad state: No element" error , I tried using a state management solution to get the sheet controller into the global willPopScope and control it from there but it meant that it needs to be rebuilt but leads to BottomNavLayout breaking again ! I think this is more like a flutter issue , i've been looking into this thread : https://github.com/flutter/flutter/issues/47088 but don't you find it weird that the BottomNavLayout has to into "Bad state: No element" just for it getting rebuilt by a simple hot reload ? Thank you again for this great package man !

Have you noticed that if you have scrollviews or list views in the tabs that tapping on the very top bar on iOS no longer does a scroll to top?

Any solution?

I tried creating unique keys but that didn't seem to do anything

   return BottomNavLayout(
      // The app's destinations
      pages: [
            (navKey) => Navigator(
                          key: UniqueKey(),
                          initialRoute: "/",
                          onGenerateRoute: (routeSettings) => MaterialPageRoute(
                            builder: (context) {
                         return NewsScreen();
                            },
                          ),
                         ),
            (navKey) => Navigator(
                          key: UniqueKey(),
                          initialRoute: "/2",
                          onGenerateRoute: (routeSettings) => MaterialPageRoute(
                            builder: (context) {
                              return SecondScreen();
                            },
                          ),
                        ),
            (navKey) => Navigator(
                          key: UniqueKey(),
                          initialRoute: "/3",
                          onGenerateRoute: (routeSettings) => MaterialPageRoute(
                            builder: (context) {
                              return ThirdScreen();
                            },
                          ),
                        ),

      ],
        savePageState:true,
        lazyLoadPages:true,
      extendBody:false,
      pageStack: ReorderToFrontPageStack(initialPage: 0),
      bottomNavigationBar: (...)