—

Thanks! :>

helena

Glad it works for you. :>

rexrainbow

Wow, that's such a nice behaviour/plugin, I didn't know that a behavior could be programmed to co-work with another behavior. It could open up to many possibilities. May I put the link to your behaviour's thread on the main post? I'll give proper credit and such :)

helena

I tried that action here, and it is working for me. Can you try downloading this simple example and tell me if this one works for you?

Create-Initialize Tween capx

part12studios

The apple example, I lost the original apple demo capx but this one should be close to what you need

Apple capx

Wertle

I can't download that example, the link is broken :(

I just tested it here, and it can call the right onEnd event on each behavior though, are you sure that is the latest tween you are using?

onEnd Test

Small fix, added loop mode and added some notes on first post about position tween to clear some confusion. (some people thinks it's a bug)

marcelokohl

Added Ping Pong and Horizontal/Vertical tween, please redownload the behaviour.

EDIT: Forgot to upload the updated behaviour, for those who already download and found out that it is actually the same as the older one, please redownload...

marcelokohl

It can be done by setting the target property to "400, 0" (to tween only x, 400 pixel right) and setting the target mode to relative.

If you want to tween only Y, 100 pixel up, you can set target property to "0, -100" and set the target mode to relative.

If you need absolute coordinate (i.e: move sprite to Y: 340, regardless of current Y), that would be a little trickier. You can use this in the event sheet:

Event: On Sprite created

Action: Set Target, target is Y (Absolute), and set value to 340

Action: Set Target, target is X (Relative), and set value to 0

However, I think I will reconsider adding that 'only X' and 'only Y' to tweened property, along with ping pong play mode due to alot of demand.

icepam

This is the example of using value tween to control SpriteFont scale

Example

AarongamerX:

That example is based on the first version of LiteTween, so even if I post the capx here, you won't be able to use it. I made another capx which is kinda the same with that one. And thanks to that I managed to find another bugs that appeared due to a recent change in it.

Apple Stretch

Wertle, clrammer

Please update the LiteTween, that latest change cause all OnEnd on all LiteTween to always fire when one OnEnd happened. And height tween accepts parameter in form x,y (which should be y only).

clrammer

Oh didn't notice that bug earlier, just fixed it. Can you try downloading again and test it?

LiteTween

Wertle:

Ah yes, it was my bad, forgot to change the height portion of the code for the tween :( I think this one fixed it, I fixed the litetween to the latest version, can you try it again?

updated

PS: also fixed the Target property

clrammer

I know how inconvenient it is for doing things like that, but that is kinda how we should do thing in C2.

The very first version of LiteTween accepts multiple tween on one behavior, like you can put 'PosTweenA' as tween name and it'll trigger correct OnEnd event respectively. It is neat and I personally liked it, but turns out that it is not easy to grasp that concept to some and it introduces 'hidden properties'. What I mean by hidden properties is those properties you can't see on design sheet, it will be modified on runtime (not very user friendly for artists usually). So the final decision is removing that 'complexity' and let C2 handles that for us.

I personally do not know the impact or overhead on performance of having so many behaviour on one object.

How about using a state machine behavior to control the tween, and put relevant code bout it in a code group (to keep event sheet tidy)?