use setOffscreenPageLimit(int limit) on the ViewPager object. From the documentation: [It set]s the number of pages that should be retained to either side of the current page in the view hierarchy in an idle state.
set setOnPageChangeListener to your ViewPager keep a variable global as private int lastPosition = 0; and in @Override public void onPageSelected(int arg0) { if (lastPosition > position) { System.out.println(“Left”); }else if (lastPosition < position) { System.out.println(“Right”); } lastPosition = position; }
E/ANDR-PERF: IPerf::tryGetService failed! I also got the above error too, but after a while, I realized that it was occurring because my code was trying to get some data from an API. I hope this might give some idea to you, I know it’s too late to answer but it might be helpful for those … Read more
You should not try to interfere with how Android manages your Fragment implementations. The default for the setOffScreenPageLimit should already be one. This means that Android will destroy old fragments when memory runs low. As long as you do not have a memory issue, just leave it be. The reason why your memory increases is … Read more
I used a negative page margin to partly show the next and the previous pages. The fading edge property can be used to make previous/next page fade: ViewPager examplePager = (ViewPager) findViewById(R.id.exampleView); examplePager.setPageMargin(-50); examplePager.setHorizontalFadingEdgeEnabled(true); examplePager.setFadingEdgeLength(30); The lastest support package (revision 4, October 2011) is also required for this to work
The FragmentStatePagerAdapter is a horrible piece of code riddled with bugs acknowledge or not by Google and so I use this code to fix this particular crash: @Override public void destroyItem(ViewGroup container, int position, Object object) { // Yet another bug in FragmentStatePagerAdapter that destroyItem is called on fragment that hasnt been added. Need to … Read more
I followed the link in jeremyvillalobos answer (which was very helpful) that led me to this workaround. public class CustomFragment extends Fragment { private static final Field sChildFragmentManagerField; static { Field f = null; try { f = Fragment.class.getDeclaredField(“mChildFragmentManager”); f.setAccessible(true); } catch (NoSuchFieldException e) { Log.e(LOGTAG, “Error getting mChildFragmentManager field”, e); } sChildFragmentManagerField = f; … Read more
There is one more event you miss: onInterceptTouchEvent. It`s must contain the same logic as onTouchEvent. My complete solution is based on this answer. It will allow you to enable/disable paging in any direction in any time you need. 1. Create enum public enum SwipeDirection { ALL, LEFT, RIGHT, NONE ; } 2.Extend ViewPager (in … Read more
Just in case anyone doesn’t read the comments of passsy’s answer, here is a summary of the useful answers: 1) Examine your getItem(int index) method very closely and look for any logic, scenarios or missing ‘break’ statements which might cause you to end up with a null fragment. 2) Check that the count returned by … Read more
Made a few tweaks in your code and it is working fine now. 1] onMeasure function wasn’t proper. Use below logic @Override public void onMeasure(int widthMeasureSpec, int heightMeasureSpec) { if (mCurrentView == null) { super.onMeasure(widthMeasureSpec, heightMeasureSpec); return; } int height = 0; mCurrentView.measure(widthMeasureSpec, MeasureSpec.makeMeasureSpec(0, MeasureSpec.UNSPECIFIED)); int h = mCurrentView.getMeasuredHeight(); if (h > height) height = … Read more