OverviewFelgo 2 Support (Qt 5) › Need navigation help for app


Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #19237

    Felgo User


    I’m new to Felgo and QML. Currently I have the following setup:


    App {
        Navigation {
            NavigationItem {
                NavigationStack {
                    Page {
             NavigationItem {
                 NavigationStack {
                     Page {


    This seems to work well, however every page gets added to the navigation bar. What I actually want is only a couple pages on the navigation bar, then 2-3 sub pages of each of those main pages to be able to navigate to that don’t appear on the navigation bar, as shown below:


    Home page

    Page 1

    ….-> page 1 subpage 1

    ……..-> page 1 subpage 1 subpage

    Page 2

    ….-> page 2 subpage 1

    ….-> page 2 subpage 2

    ……..-> page 2 subpage 2 subpage


    Where I’d like to have none of the subpages appear on the navigation bar as certain actions in their parent pages need to be taken to access the sub pages. I hope this makes sense.


    I’ve tried using Components outside the Navigation {} section and using NavigationStack.push(subpageId) but that only works for a single subpage, it fails when I try to access a 2nd level subpage from the 1st level subpage.


    Should I be approaching this completely differently? Can I use the Component subpage concept but do something special for the 2nd level subpages?


    I hope this makes sense and someone can help me out.


    Thank you,



    Felgo Team


    the Component approach is correct! But you have to keep one thing in mind when working with the second-level page from your first-level page:

    • The Component is not an actual Page, it is just the template how the page will look like when it is created.
    • As long as no Page is created / pushed to the NavigationStack based on the Component, you won’t be able to access the Page and its properties.
    • As soon as you’ve created/pushed the Page, you can access and work with the actual Page e.g. via NavigationStack::currentPage.
    • There are also Page lifecycle signals like onPushed, onPopped or the isCurrentStackPage property, which you can use for the Page.

    You can also have a look at the Felgo Example Apps to see how Navigation und Sub-Pages are handled there.


Viewing 2 posts - 1 through 2 (of 2 total)

RSS feed for this thread

You must be logged in to reply to this topic.

Voted #1 for:

  • Easiest to learn
  • Most time saving
  • Best support

Develop Cross-Platform Apps and Games 50% Faster!

  • Voted the best supported, most time-saving and easiest to learn cross-platform development tool
  • Based on the Qt framework, with native performance and appearance on all platforms including iOS and Android
  • Offers a variety of plugins to monetize, analyze and engage users
create apps
create games
cross platform
native performance
3rd party services
game network
level editor
easiest to learn
biggest time saving
best support