Normally when you tween something, you can make a call to
Tweener.removeTweens(this) beforehand, to remove any current tweens. If you do
this before a call to addTween() (or any other function that calls init()),
Tweener will crash as _specialPropertySplitterList is null. Technically we
could call init() ourselves, but there's no check in init() to see if the
engine is already inited, and if so, quit out, meaning that it's possible to
clear the objects created.
Q. What is the expected outcome? What happens instead?
Tweener should call init(), and shouldn't crash.
Q. What code will reproduce the problem?
Just call Tweener.removeTween() before adding anything
Q. What version of the class are you using, and under which development
environment (IDE version, compiler, etc)?
It's present in the latest download (tweener_1_33_74_as3.zip)
Please provide any additional information below. Also, please attach *small*,
sample files with minimum functionality to reproduce the problem if possible.
Original issue reported on code.google.com by divilly....@gmail.com on 28 Sep 2012 at 9:33
Original issue reported on code.google.com by
divilly....@gmail.comon 28 Sep 2012 at 9:33