But: calling nav.setRoot() is not desirable in my case. The only reason I need the tabs is for their ability to pre-load all the pages and keep them in memory (for speed, because initialization of some of these pages is heavy in my app). The nav.setRoot() solution destroys and recreates pages on every tab switch, but that’s what I was trying to avoid by using the tabs and their built-in navigation.
Is there a way to use the two together without calling nav.setRoot() - by just selecting tabs as we used to do with, e.g. app.getComponent('nav-tabs').select(1) ?
does not seem to work - it only works with navcontroller, but no other component - when decorating a property for any other component, the property never gets initialized, it remains undefined.
Any help on how to get to select tabs from the app class methods would be greatly appreciated. Thanks.
I have the same problem, where my tabs are disappearing when I select a page from the menu and this solution is not working for me, does the conference app have the complete example for this scenario.
Well i have seen this approach everywhere i googled. But most of the times we need tabs on all pages which are in menus but not in tabs. i,e we need to show tabs on pages which are not in tabs but in menus. I hope you understand my issue please help or share some docs regarding this stuff. As i’m working on a complex app where there are 3-4 tabs but more menus & i need to maintain the tabs on every page.