fix for issue with transforms being left after drop #156
Conversation
|
Not sure if there is a way to have the events stop firing after a drop occurs (it seems to only happen in some cases). I just did some debugging to get my information (placed logs in _drag, and reset and saw what order they were happening in when things went wrong). |
|
It was also unclear if I should make my changes on the 1.x branch or master. I tried out the master branch in my application, and it seems to have issues with performance, and also it seems as if my "handle" on the element is coming loose. I did not dive into this. perhaps there is an api change I am not aware of. |
|
I do have a version of my changes for the master branch as well. |
|
I have the same problem and this patch seems to solve it. |
|
Thanks so much for this patch and sorry it hasn’t received any attention. I can’t make any exact promises about when it’ll be merged but don’t let us off the hook, we’ll get there! |
|
Thanks so much for the patch! I’ll try to release it later today. |
fixes #132.
_dragwas being invoked afterresetwas called on the item, and after a drop.