I have to implement navigation structure like iOS or you can say like browser. where in my application it is like i have 3 tabs and for each tab there is flow of multiple fragments like
Tab 1 --> Fragment 1--> Fragment 2--> Fragment 3
Tab 2 --> Fragment 1--> Fragment 2
Tab 3 --> Fragment 1--> Fragment 2--> Fragment 3--> Fragment 4
And navigation is like when user switches tab then can view last opened Fragment of that Tab and on pressing Back should go back to previously opened Fragment of that Tab. All these Fragments load from single Fragment Activity so what I'm thinking is to manage Navigation manually by creating three different stacks keeping track of opened Fragments in those Tabs.
What i want is a method by which i can bring previously added fragment to front without pop of any other even there are some which added after that fragment. And on back press I'll pop the current fragment and bring in front another previously added fragment according to my own managed stacks.
I searched for method to bring in front previously loaded fragment by tag but they will pop all the fragments loaded after that fragment which is not acceptable for me.
You can try
getSupportFragmentManager().beginTransaction().attach(fragmentA).commit;
or
getSupportFragmentManager().beginTransaction().show(fragmentA).commit;
and hide other fragments you have in your FragmentActivity by looping through all given by
getSupportFragmentManager().getFragments();
//This gives list of fragment in stack
Related
Suppose I have different fragments within an activity in backstack such as [1]->[2]->[3]->[4]->[5] with Fragment 5 presently visible on the screen. Now I want to go to Fragment 2 without destroying Fragments 3 and 4 on a single press of a button. How can this be done?
So if for example I had 4 fragment managers, would there be 4 seperate back stacks to handle?
Im looking to create a tabbed application that uses a bottom nav bar to switch between fragments. But within each tab the user can progress through to different areas of the app. I need it so that no matter how far they get in to a tabs flow, if they clicked on another tab, then came back to the previous tab, they would still be at the same place they left off.
So would using multiple FragmentManager instances (one for each tab) solve my issue?
In my case I have 4 fragments, one for each tab. So if im on tab 1 and go to fragment 4 in tab 1, if I then tap tab 3 and go to fragment 2 in tab 3, if i then go back to tab 1, i should still see fragment 4 of tab 1. But im not sure how to set this up.
You should be fine using two Fragment instances for the tabs in the nav bar, and use each tab Fragment's getChildFragmentManager() method
I have an app which contain three tab with three fragment mainly A,B,C lets suppose I am on tab 2 which contain fragment B when app goes in background and again resume then fragment A is showing instead of fragment B. Ho do I resolve that?
I have a single activity that uses a bunch of different Fragments. I have a TabContainer Fragment that holds a TabLayout which uses a ViewPager to handle tab navigation. Each Tab is its own Fragment.
In one of my tabs, I want to tap and place a fragment on top of my Tabbed fragment. This is meant to be a "details" sort of screen, so I don't want the tabs to be visible. I'm using this and it works as intended:
fragmentTransaction.replace(android.R.id.content, fragmentToDisplay).addToBackStack(null).commit();
Now, when I navigate back, the content in my tab is empty. The content in the tab directly next to that tab is also empty. When I navigate two tabs away, the content is recreated and the normal functionality returns. Why is content not being recreated on the tabs initially when I remove my "detail" fragment?
It turns out that I was simply not passing the correct FragmentManager to the FragmentStatePagerAdapter.
I needed to call getChildFragmentManager() on the Fragment, not getSupportFragmentManager() on the activity.
Thanks to these two posts for the answer:
Fragment in ViewPager not restored after popBackStack
and: Replacing ViewPager with Fragment - Then Navigating Back
I have a fragment that hosts a ViewPager with 3 fragments, 2 of them contain ListView (not inherits FragmentList)
The problem is:
If I click on one of the items in one of the list the application navigates me correctly to a new fragment, but, if I press the back button and go back to the ViewPager, a can see a blank fragment, only the first fragment who didn't have ListView is created, none of the other fragments are displayed, nor even their onStart is called
What's wrong? I suppose the fragment is not attached again, how can I solve this issue?