android-nested-fragment

I have a Fragment that has a FrameLayout . This first fragment (A) loads inside its Framelayout another fragment (B). When I call getParentFragment from inner fragment (B), I get null . How should this method be used properly? Eurig Jones getParentFragment() was introduced in API level 17 (Android 4.2). Android 4.2 introduced the idea of nested fragments (fragments containing other fragments). Calling this results in null if the fragment has a parent which is an Activity. Have a look at this . If you are using support library then you can use getParent(), may be you need to use

I would like to create a ViewPager (with three items) where each of its view is another ViewPager (with two items). User then swipe items like this: ViewPager1[0] ViewPager2[0] ViewPager1[0] ViewPager2[1] ViewPager1[1] ViewPager2[0] ViewPager1[1] ViewPager2[1] ViewPager1[2] ViewPager2[0] ViewPager1[2] ViewPager2[1] How would that be possible? override canScroll in the parent ViewPager: @Override protected boolean canScroll(View v, boolean checkV, int dx, int x, int y) { if(v != this && v instanceof ViewPager) { return true; } return super.canScroll(v, checkV, dx, x, y); } Try this: public

Here's the scenario: Activity contains fragment A , which in turn uses getChildFragmentManager() to add fragments A1 and A2 in its onCreate like so: getChildFragmentManager() .beginTransaction() .replace(R.id.fragmentOneHolder, new FragmentA1()) .replace(R.id.fragmentTwoHolder, new FragmentA2()) .commit() So far, so good, everything is running as expected. We then run the following transaction in the Activity: getSupportFragmentManager() .beginTransaction() .setCustomAnimations(anim1, anim2, anim1, anim2) .replace(R.id.fragmentHolder, new FragmentB()) .addToBackStack(null) .commit() During the

With Android 4.2, the support library got support for nested fragments see here . I've played around with it and found an interesting behaviour / bug regarding back stack and getChildFragmentManager() . When using getChildFragmentManager() and addToBackStack(String name), by pressing the back button the system does not run down the back stack to the previous fragment. On the other hand, when using getFragmentManager() and addToBackStack(String name), by pressing the back button the system returns to the previous fragment. For me, this behaviour is unexpected. By pressing the back button on my

I have a fragment interface with tabs along the bottom which open different fragments in the main view. I have one particular fragment which is a list of items. If the user selects one of the items in this list, another fragment opens which contains a viewpager which scrolls horizontally between all of the items in the list in the previous fragment. This works great. The viewpager uses a FragmentPagerAdapter to display the items. The problem comes when the user selects an item in the list, views it, then hits the button on the tab bar to go back to the list, then selects another item. The

I need to place a ViewPager inside of a fragment, but I have two fragments, Fragment 1 is my MENU, and Fragment 2 I want to use as a ViewPagerIndicator. But a fragment can't have another fragment... what do I need to do for that? Ryan S Starting in Android 4.2, there are nested fragments. http://developer.android.com/about/versions/android-4.2.html#NestedFragments The support library now also includes support for this for older Android versions. So you can do something like this: @Override public void onViewCreated(View view, Bundle savedInstanceState) { super.onViewCreated(view,