Here's a small addition that should nevertheless come in handy in many situations:
In the past, anyone who wanted to animate the "color" property of a Starling image from one value to the other will have noticed that a standard tween of the value "0xffffff" to "0x0" does not yield the desired result: instead of a smooth change from white to black, you literally see all colors of the rainbow in short succession.
Equally annoying: if you want to rotate an object from, say, -170 degrees to +170 degrees, you'd expect it to turn by just -20 degrees. Instead, Starling would rotate it to the other direction, over an arc of 340 degrees. Most of the time, that's not what you want.
With the changes of the tween API that I just committed, it's finally easy to avoid that.
Any property name that contains the string "color" (or "Color") will be treated as such: Starling will automatically animate the color channels individually, resulting in a smooth transition.
If you want the same to happen for a property that does not contain such a string, you can append the string "#rgb". I call this a "property hint". E.g.:
tween.animate("color", 0xffffff); tween.animate("farbe#rgb", 0x7f7f7f); tween.animate("couleur#rgb", 0x112233);
When working with rotations, you have to opt-in to the new behavior by appending one of the property hints "#rad" or "#deg", depending on the unit of measurement.
I decided not to change anything for the standard "rotation" string; sometimes you actually want the tween to use the longer arc. For example, you probably wouldn't want your clocks to run backwards, right?
tween.animate("rotation#rad", Math.PI); tween.animate("rotation#deg", 180); // or tween.rotateTo(Math.PI); // rad tween.rotateTo(180, "deg");
I hope you like this little change!