"${_Ellipse}": [ | |
["style", "top", '214px'], | |
["style", "left", '163px'], | |
["motion", "location", '193.60000038147px 245.20833396912px'] |
If I create x/y tweens but later decide to replace them with a motion tween, the object still retains some of its original positioning, and will reset to the wrong position when jumping around the stage with stop() (and then motion path from this new location). An example can be seen here:
http://testsites2.b-lex.com/tests/arnold/edge_motionpath/
See the circle's initial path. Clicking it sends a stop(0) to the stage, and a play() a second later. It will reset to the wrong position, and start playing it's path from there. The "wrong position" is offset by exactly the original top/left position it started with in the initial x/y tween
The full project is here:
http://testsites2.b-lex.com/tests/arnold/edge_motionpath/converted_to_ motionpath.zip
The steps to recreate it are:
- create an ellipse
- set a Left motion tween from 0s to 1s (using the pin) from left:53 to left:222
- switched to motion paths (with time still at 1s)
- the elippse jumped back to its initial position. moved it somewhere else
- created a motion path tween from 0s to 1s using the pin
(though I didn't test whether using the pin is actually necessary to trigger the bug)
If you're hit with this and don't feel like deleting the symbols and rebuilding the motion paths from scratch, the workaround is to manually edit the JS file and removing the top and left positions for this symbol:
"${_Ellipse}": [ | |
["style", "top", '214px'], | |
["style", "left", '163px'], | |
["motion", "location", '193.60000038147px 245.20833396912px'] |
but i'd suggest backing up your project before you try this at home.