If you have used Scroll Components and draggable elements in your prototypes, I'm sure you've encountered the infamous 'this._simulation.y' bug. I went full mythbuster on this and I can say that there's always a solution for that bug. You just have to rethink the logic of your code.
Maybe I should write a post about this to go in-depth about my findings, but for the time being these examples might suffice. Download the projects and look at the code. : )
A few months back Randy Huynh shared this example: http://share.framerjs.com/l1k0oo93a800/ Please take a look at the code. (To trigger the bug, drag the element, stop dragging WITHOUT releasing the element, THEN release).
Here's my fix: http://share.framerjs.com/xfepzd72rmsu/ Check the code, seriously, that fix is a joke.
Here's another example, using dynamic objects: http://share.framerjs.com/84wptf2nof20/
Things to keep in mind (not all of these are shown in the previous examples):
- Double-check your code if you're using conditionals and '.animate' inside your DragEnd/ScrollEnd events. Your solution might be right there.
- Consider creating an 'Animation' instead of using '.animate' (see Docs).
- X's befores Y's!!
- TouchEnd events trigger BEFORE DragEnd and ScrollEnd. Try to use that in your favor if you're using flags to change the state of things.
I know all of this is a bit abstract, but I hope it helps!