Steps for implementing viewpager: Adding the ViewPager widget to the XML layout (usually the main_layout). Creating an Adapter by extending the FragmentPagerAdapter or FragmentStatePagerAdapter class.
yes...you can use View instead of Fragment in viewpager.
use AsyncTask to set the adapter for viewPager. It works for me. The asyncTask is to make the original fragment complete it's transition. and then we proceed with viewPager fragments, basically to avoid recursion.
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
mView = inflater.inflate(R.layout.team_card_master, container, false);
mViewPager = (ViewPager)mView.findViewById(R.id.team_card_master_view_pager);
final Button button = (Button)mView.findViewById(R.id.load_viewpager_button);
button.setOnClickListener(new OnClickListener() {
@Override
public void onClick(View v) {
mViewPager.setAdapter(mAdapter);
button.setVisibility(View.GONE);
}
});
mAdapter = new ViewPagerAdapter(getFragmentManager());
new setAdapterTask().execute();
return mView;
}
private class setAdapterTask extends AsyncTask<Void,Void,Void>{
protected Void doInBackground(Void... params) {
return null;
}
@Override
protected void onPostExecute(Void result) {
mViewPager.setAdapter(mAdapter);
}
}
You can use FragmentStatePagerAdapter
instead of FragmentPageAdapter
. It will remove fragments for you.
I just ran into this same problem. I had a Fragment
that needed to host a ViewPager
of Fragments
. When I stacked another Fragment
on top of my ViewPagerFragment
, and then hit back, I would get an IllegalStateException
. After checking the logs (when stacking a new Fragment
), I found that my ViewPagerFragment
would go through its lifecycle methods to stop and destroy, however its children Fragments
in the the ViewPager
would stay in onResume
. I realized that the children Fragments
should be managed by the FragmentManager
for the ViewPagerFragment
, not the FragmentManager
of the Activity
.
I understand at the time, the answers above were to get around the limitations of Fragments
not being able to have children Fragments
. However, now that the latest support library has support for Fragment
nesting, you no longer need to hack around setting the adapter for your ViewPager
, and passing getChildFragmentManager()
is all you need. This has been working perfectly for me so far.
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
mView = inflater.inflate(R.layout.team_card_master, container, false);
mViewPager = (ViewPager) mView.findViewById(R.id.team_card_master_view_pager);
mAdapter = new ViewPagerAdapter(getChildFragmentManager());
mViewPager.setAdapter(mAdapter);
return mView;
}
I used Handler.post()
to set adapter outside of original fragment transaction:
@Override
public void onActivityCreated(Bundle savedInstanceState) {
super.onActivityCreated(savedInstanceState);
mHandler.post(new Runnable() {
@Override
public void run() {
mViewPager.setAdapter(mAdapter);
}
});
}
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With