I was saying that too, that’s why I made this application (I make every app because I need them). Therefore, if you need an Eiffel Tower in your game, you need to decompose it into convex polygons and then to enter their coordinates vertex by vertex. The Box2D physics engine, like every other physics engine ( Chipmunk, Farseer, etc.), can only check collisions between convex polygons, with at most 8 vertices. I added implementations for primitive types, like TweenableInt, TweenableFloat, etc.Īnother post, this time to present the recent 1.0 release of the Box2D-Editor application. It should be used when you don’t care about tween types since there should only be one possible. at call time)Īlso, I added a SimpleTweenable interface, that extends Tweenable. targetCurrentRelative(…): target values are the params added to the values at current time (ie. targetCurrent(): target values are the values at current time (ie.
targetRelative(…): target values are the params added to the start values (at start time, after delay) target() method that is used to set the target value(s) of an interpolation, there is now the following ones: Otherwise, a ton of useful stuff was added to the Tween API. Create some powerful animation sequences!
Texturepacker for ui app design code#
Have a look at the following code snippet to understand how groups can be used to create complex and powerful sequences: I broke the TweenGroup API, but with a good reason: groups now support nested sequences, and they are pooled (if Tween pool is activated).
Texturepacker for ui app design update#
I recently released a major update to the Universal Tween Engine (if you wonder what is this lib, see this post).
0 kommentar(er)
