First and last Views getting destroyed even after using DEFAULT_BOUNDARY_CASHING true

Question

First and last Views getting destroyed even after using DEFAULT_BOUNDARY_CASHING true

Opened this issue 9 years ago · 3 comments

summers314 commented 9 years ago

Answer 1 · 2016-05-11T07:02:09.000Z

Just call setOffscreenPageLimit() with you pager size.

Answer 2 · 2017-07-25T03:06:40.000Z

setOffscreenPageLimit() should set adapter wrapper's count or real adapter's count ?

Answer 3 · 2018-07-24T10:04:20.000Z

LoopPagerAdapterWrapper.destroyItem() has a bug: realPosition can be less than realFirst, which appears to be an unexpected situation. Changing if (mBoundaryCaching && (position == realFirst || position == realLast)) to if (mBoundaryCaching && (position <= realFirst || position >= realLast)) significantly improves the behaviour around destroying views.

A bug remains: when swiping backwards from the start, the last item is still recreated. This only happens the first time, however.

I was considering making a PR for the change, but given it's still buggy I thought I'd just contribute a suggestion, as I don't have the time to delve deeper now.