anty21ro

It is exactly what I am thinking also way back then when I made EaseTween, EaseTween has this functionality, adding a wait before starting tween and a delay of pause after a tween. It also has alot of control, like PingPong, Loop, etc. But LiteTween is designed to be controlled from the event sheet, it is not EaseTween. The right way to do it is simply add 'Wait X seconds' action before 'Start LiteTween'. If you really need that functionality, I suggest you download the EaseTween again and check if it will suit you more. Despite it is not being developed anymore, some of my old projects that is still running still use it heavily without problem.

AlexFrancois

Umm. The answer is both yes and no.

For setting the starting value, you can do something like 'LiteTween > Set Value' then just put variable into it.

For setting the target value, you can also do 'LiteTween > Set Target' then set 'str(x)' your variable into it.

But yeah, you can't set variable as target value in the object property at design time.

Joannesalfa

Oh, there is an action 'Set Value' to set the start Value.

On mouse click

> Litetween Set Value = 15

> Litetween Start tween

Flodcp

I am not sure with that problem, if you have a capx i might be able to help more. But try this first, would changing it from on Collision (which is a trigger), to on Overlap works?

—

Changing it to "start, target" would make alot of other users of LiteTween who have used the old way of "target" refused to work (some used really alot of litetween in their old project).

The other way would be to add something like "Value (start,target)" tweened property to take 'start, target' parameter, but this is confusing because it will be inconsistent to how other 'target' works. I am sorry I think I shouldn't add this one. And thank you for answering the question for me about XDK/Cocoon export. :>

Sorry for the late reply guys,

jomo

That is the correct behavior of how EaseInBack, EaseInBounce etc works.

I'll try to explain EaseInBack and EaseOutBack using ordinary words.

So in height tween of EaseOutBack, it works by making its height bigger, then it will exceed 68 pixel, after that it will return to the 68 pixel with.

In height tween of EaseInBack, it starts by making its height smaller, then grow its height bigger until it reach 68 pixel.

But in the case of EaseInBack since it starts at zero, the height became negative, which cause it to turn upside down. This is how C2 behave, if you set height or width to negative value it will flip or mirror (actually that is how it is coded in javascript), so I can't do anything with it. Clamping it to zero in litetween using javascript would make other people who expect it to go negative unsatisfied. So if you still want that effect, you should clamp it to zero in C2 events.

I made a simple example here:

https://dl.dropboxusercontent.com/u/553 ... anged.capx

Are you sure you don't want EaseOutBack instead?

—

Ok, I put the answer on the other thread.

—

Both Ashley and 99Instances2Go are true. The problem lies in the structure of the code and the use of trigger insides of the else clause which the trigger assumes it is a true condition. I am not even sure how to fix or even if it is fixable, so I will pass on that.

If you just want to focus on finishing the job you can just use 'Compare Progress' = 1, which mean it has reached the end of the tween. Compare Progress is a condition, which is not a trigger like On End, so it will work

Nitro187

It is a bug in the mirror/flip handling code in litetween, i think TrickyWidget mentioned about this as well before, but i didn't catch what he meant during that time.

I fixed the bug once more, hopefully this time it will finish it once and for all. Mirror and Flip are always confusing to deal with due to the negative width etc.

Please redownload the behavior in the first page.

Cipriux

Sure it can do that. My wild guess for that problem is that you use Enforce instead of Compromise. Because of that, one of the tween won the enforced coordinate for the other. If you want the second graph which looked like a circleEaseOut to me, you need to tween linearly for X (Horizontal tween), and tween easeOutCircle for the Y (Vertical tween).

I made a simple capx, I hope this is what you need.

https://dl.dropboxusercontent.com/u/553 ... lotxy.capx

Cipriux

Thank you for noticing that bug, that's a simple typo, I just fixed it. The download link is on the first page like usual. Please tell me if it is still not working correctly.

Ragevortex

You should use Enforce mode > Enforce. Don't use compromise for this case.

krisnk

I tested on chrome browser and it worked fine, can you be more specific about the steps to reproduce the problem? And also, this is a wild guess but it is a behaviour, not a plugin, so you should put it into behavior folder, not plugin folder, maybe that is why?

UltimateArceus3

It does work with expression to some extent; Though you need to know how to convert numerics into strings and vice versa.

I don't really understand the problem you encounter, are you using Set Target X and Set Target Y? Or are you using create/initialize tween? Sometimes using Set Target X and Set Target Y would be more convenient, depending on the case. I could help more if you could provide me with a simple capx describing what you want.

—

I am not sure either. If it is on the weaker device with less processing power, it might be because LiteTween is using precalculated array instead of having to calculate the lerp every tick, so it is lighter on the CPU. But if it is on an adequate PC/mobile, lerp/dt should have about the same smoothness with linear LiteTween.

powerof2

I just checked and it is working fine, which link is not working?

justifun

It is a string, if it is a position tween you can use "700,200" in the target to tween to x=700, y=200. If you want to use variable let's say MyTargetX and MyTargetY, you can turn those two variable into string by entering

MyTargetX & "," & MyTargetY

into the target field.