ACTION_CANCEL was doing the same as ACTION_UP

[wdullaer]

This causes issues when a parent view tries to steal a MotionEvent using onInterceptTouchEvent (such as a DrawerLayout opening the side menu).

I've added an implementation for ACTION_CANCEL (looking at the latest romannurik code). This solves issue #65 on your issue tracker.

I hope I did this pull request right, I'm a bit new to the entire Github thing.

[nhaarman]

Thanks! However, #65 doesn't have anything to do with swipedismiss. Do you mean #64 ?

[wdullaer]

Yes indeed #64. I must have made a typo.
Op 8 jan. 2014 14:24 schreef "Niek Haarman" notifications@github.com:

Thanks! However, #65https://github.com/nhaarman/ListViewAnimations/issues/65doesn't have anything to do with swipedismiss. Do you mean
#64 https://github.com/nhaarman/ListViewAnimations/issues/64 ?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/115#issuecomment-31830315
.

[nhaarman]

cb9b979 & 55e6dca

[ishish]

Note only the change for SwipeDismissListViewTouchListener was taken from the Pull request. The issue still occurs for the ContextualUndoListViewTouchListener. I split the up and cancel and sent the Cancel event to the following method:

private boolean handleCancelEvent(final View view, final MotionEvent motionEvent)
{
     if (mVelocityTracker == null) {
         return false;
      }

      if (mDownView != null && mSwiping) {
          // cancel
          animate(mDownView).translationX(0).alpha(1).setDuration(mAnimationTime).setListener(null);
      }

      mVelocityTracker.recycle();
      mVelocityTracker = null;
      mDownX = 0;
      mDownY = 0;
      mDownView = null;
      mDownPosition = ListView.INVALID_POSITION;
      mSwiping = false;
      return false;

}