Oh, and I forgot to tell you, the newest litetween is kinda different with the old one due to talk I had with several ppl on the forum.

You no longer need to specify initial coordinate/etc for tween, it always tween from current to target.

If you want to tween from x,y to x2,y2 (not from current to x2,y2), simply set the position to x, y first before setting target. Because setting target automatically readjust initial to current position.

And, it is now much more stable IMHO... some bug fixes like opacity fix etc...

JKID: A lot have changed in LiteTween since the last time we talked about it :o... Maybe you can try the newest version?

dl.dropboxusercontent.com/u/55358831/lunarray.litetween.zip

I could also check how is it if you could reproduce the error in a simple capx.

Small fixes for annoyances posted...

Also removed old litetween zip.

NECROKRIEG

How about something like this?

ScrollTo capx

You only need to put more clickspot at the 'map' and set their respective targetx and targety to anywhere you want.

I think there already are some tutorials on the site about how to make a shooter...

Maybe something like this?

scirra.com/tutorials/53/how-to-make-an-airplane-shooter-with-c2-video

I think you should turn off the lerp of the button 1-2 when you go to button 3-4, and vice versa. If I'm not mistaken about what you're trying to do, the lerp of button 1-2 conflicts with the button 3-4 because you did not set the boolean to false.

California

But I though it should work too for Textbox. Though maybe there are some quirks happening since textbox is a DOM element.

jayderyu

I just found that set duration {1} bug. Fixed it, I'll post it later on.

As for repeat action, that would be like slowly evolving litetween and bringing back easetween again. One of my reason of making litetween is making it simple. For that I get rid all of the playmode and move it out to event sheet. It does cost more events that way, but well, more C2-ish.

California

Something like this?

Size tween

Oh and, you can also just play the tween every 1.0 secs, without re-setting the target, it will work kinda the same too.

Just one event, "every 1.0 secs > LiteTween start from beginning". :>

Kenney

Ah, I see, I've checked the capx. You shouldn't be setting target every 1.0 secs (what I exactly mean is that you should set initial beforehand), it will cause the initial to be set everytime you set the target (to object current position).

It goes kinda like this:

1. Before the first tween, the object position is at 302,241.

2. At 1.0 secs, c2 called set target to absolute 100,100. Because of this call, it also set the initial of the tween to 302, 241. So, right now, the tween goes 302,241 to 100,100.

3. The tween plays, and the object is now at 100,100.

4. After another 1.0 secs, c2 called set target 100,100 (absolute) again. But now, the object is already at 100,100. So it make a tween for 100,100 to 100,100 (which does nothing).

The right way to set initial now is simply by setting the object position before you set target. If you add "Set Position to 302,241" before setting the target it will act just like setting initial.

PS: Maybe I should include a capx about it :>

dl.dropboxusercontent.com/u/55358831/helping/tweenSample.capx

jayderyu

Could you try this one? I modified alot and removed "Set Initial" too.

LiteTween 0.9

Kenney

I found the problem in the old lite tween, but i'm not going to maintain two version of litetween :(, so eventhough I fixed those bugs, you might want to try the v0.9.

PS: I also made a simple demo for it...

Demo CAPX

jayderyu

I think I see your point there, the string parsing and all are unintuitive. I think I'll try going with your suggestion for set target, and properly hide the "current" and "relative" etc from it. It is not very nice for newcomers to C2. I'll put that here after I finished it today, hopefully tomorrow it will be ready.

About the tween naming system. I also agree that removing the naming system and go with C2 way of naming the behavior in the IDE is more eventsheet friendly. So yeah, maybe for litetween I should keep it small and should not trying to input too many features in it. Let's see what I can do with it.

Going back to the reason I created LiteTween, is because with easetween I inputted too many features in it till it became so big (old habit dies hard). So simplifying the interface and removing features to the absolute essential is still very relevant to litetween.

Thanks for the suggestion, I'll go with that route now.

Kenney

Can you please show it in a small capx? Because it works for me here with enforce and target (100,100). But maybe you would want to wait till I do redux like what jayderyu suggested.