Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implementation for drawer swipe, as described in #905
Usage
SimpleSwipeCallback
dp
) towithSwipeLeft
andwithSwipeRight
during constructionViewHolder
must implementIDrawerSwipeableViewHolder
to indicate whichView
will slide with the swipe gesture. The views below may display clickable buttonsSimpleSwipeDrawerDragCallback
to enable drag + swipeImportant / For your consideration
When the sliding view has been swiped, the buttons located below are visible on screen, however, when tapping on them, the default Android touch even dispatch mechanism doesn't transmit the tap event to the buttons : any click on the exposed surface just swipes the item back to where it came.
To enable the touch events to actually reach the buttons below, I had to implement a small hack that uses
OnTouchListener
(seeSimpleSwipeDrawerCallback.RecyclerTouchTransmitter
).It works well but has a price : any
OnTouchListener
the user would have previously set on theRecyclerView
will be overriden byFastAdapter
's ownOnTouchListener
.Is that acceptable to you ?