Thanks for trying it out. I was planning to fix it all at once and make a proper demo (kinda like a documentation in form of a demo), but i got distracted with things irl...
As for initial or target string, it currently accept these types:
"current": The current object's opacity, angle, or position depends on the context. This is replaced by the said value when the tween is created, not when the tween is played. Example: tween got created when the object is at (120, 30), current will be replaced with (120,30) when it is first created.
"relative(x,y)": where x, y is relative to the current position, angle or opacity. It can accept negative value. Also, this one got replaced with the said value when the tween is created.
"x,y": the x,y coordinate of the target or initial string. Depends on the context of the tween, it can also accept single value as in "100" for opacity etc.
About tween name, it accepts "all" just fine here, even for the set target too. Could you provide a capx for it?
The special tween name would be "default", "all", "earliest" and "furthest". It depends on the context.
"default" is the default tween which property is changed in the IDE. It is not really a special one though. It's just a tween that got named "default" and got created when we include the behavior.
"all" means that you target all the tween in the behavior at once. It works in almost all of the action (except set parameter/create tween for kinda apparent reason :(, will fix that up later).
"earliest" and "furthest" are captured only on progress checking, because it didn't make sense in other context.
PS: There are some bug fixes happening when I made this post, please update it to the latest behavior. Thanks :>lunarray2013-06-22 19:14:08