Open MFlisar opened 1 year ago
Unfortunately, I currently do not have the capacity to look into this problem.
This sounds like it may be a problem, however, this would also lead to behavior changes for all usecases (given the different firing)
It may be worth to adjust this behavior in a future version. Happy to look into a PR, if you'd like to contribute these changes
About this issue
I see the same issue like in the video here: #991 and I do use stable ids in my adapter...
What I see is following
itemTouchDropped
is called followed byitemTouchStopDrag
(which seems to be intended, although it seems wrong imho)itemTouchDropped
=> this triggers a data update and updates the adapter data which may happen during a running animation...Problem
itemTouchStopDrag
stops the drag animation, this means the item appears at its original position again although the back animation move animation is still runningWork around
I delay the the drop data update until the
itemTouchStopDrag
is called after a drop.Here's my code:
Question
What's the reason to not delay the
itemTouchDropped
until afteritemTouchStopDrag
? This seems unlogical to me...Details