Search the Community
Showing results for tags 'killtweensof'.
Found 9 results
-
Hi all, I've got an issue with using a killTweensOf following by a fromTo method. Here is a codepen for explaining the issue https://codepen.io/manuelodelain-the-lessful/pen/eYddYzQ The expected behavior here would be that the blue square fades from 0 to 1 each times I hover it. If I hover the blue square multiple times very quickly the animations plays as expected but at the end of the animation the opacity reverts to 0. If I don't use killTweensOfthe issue doesn't occure. Thanks,
-
It possible to add a native event like: .eventCallback('onKill', function) or maybe a way to force onComplete when is kill ? Example context: pointerdown_Axi3d(e){ // blink renderable objs gsap.fromTo( $objs.LOCAL.unique().map(o=>o.link), 3, { renderable:false }, { renderable:true, repeat:-1, ease:SteppedEase.config(1), id:'blinkRenderable' }) .eventCallback('onComplete', myfunction); } then if i kill pointerup(e){ gsap.killTweenById('blinkRenderable'); } how i can say, kill but plz call the onComplette event ! ? My target is when i kill the tweens lots, i want force restore the value renderable to true inside a event function.
-
1) I want to start a tween on an x-parameter but there is a possibility another TweenLite is still tweening the same value. Now I think pretty highligh about Greensock and it wouldn't surprise me if it's clever enough to stop the running tween when starting a new one. But I'm not sure. On the moment I'm having a killTweensOf() before starting the new one, but is that really nececary? Or does TweenLite indeed kill the running tween when starting the new one on the same value-parameter? BTW, 2) I was about to killTweensOf a value uses with the PixiPlugin (which is pretty convenient for large projects BTW!). But I'm not sure how to killTweensOf parameters when we're using plugins. I can't find it in the greensock help, but might be overlooking something there. Is this the right approach if we want to kill all tweens tweening the x-position via the PixiPlugin?: TweenLite.killTweensOf(this.bmp, { pixi: { x: true } }); Or should we leave pixi and just use the x-value instead (so Gsap 'underwater' knows somehow the x goes through the pixiPlugin)?: TweenLite.killTweensOf(this.bmp, { x: true }); Thanks in advance! And I am happy tweening all day long. This lib is just so well made, it's just so fun to use! Especially together with svg, pixi and threejs! :) -
After running killTweensOf(), change the properties autoAlpha. It does not work. killTweensOf() is in the onComplete. i use 2 tweens,because I want to use different ease http://codepen.io/lzy100p/pen/bgRVVW
-
Hello, Not sure if this is a bug or by design. I suspect the latter of course In the AS version, KillTweensOf has a second parameter that will call the onComplete function. Here is a thread about that... http://forums.greensock.com/topic/1932-can-a-killed-tween-still-trigger-oncomplete/ In the JS version, KillTweensOf does not have this parameter. I'm curious, should it be there? My work around was to use KillAll which does use the onComplete param. This worked for my situation but I could see this being a problem for others. Thanks!
-
Hi, I have big problem with killing The problem: 1. I have 5 functions fired one by one with "onComplete". 2. I need to kill any tweens from this functions in any time, and it works properly when I kill any of these functions for the first time. 3. It doesn't work properly when I fired these functions and try too kill one again. 4. It does look like "the killing machine" remember position of myElement when the first "kill" was fired and move in a blink myElement to this position, then of course kill the tween. Should I clear something or maybe something else? Best Regards
-
I was playing with killTweensOf, and after a few hours of problems I discovered that the documentation is not updated correctly between v11 and v12 (it reports a "complete" parameter that does not exist anymore in v12), that the version I was using was sufering of a bug (the second parameter was an Object intead of a Boolean as declared in the documentation;,updating the libs it has been fixed, but...), and that the second parameter in the new libs version is not "complete" anymore, but "onlyActive"! What a mess! I now wonder if to force tweens completion before killing them I have to use the function you suggested in this thread http://forums.greensock.com/topic/7342-killtweensof-not-working-and-there-is-no-longer-a-complete-param/?hl=completion#entry27578 or if there is a built-in function to automate it. Why did you remove the complete parameter? Thanks
-
Hi, This is not working for me: TweenMax.from(this, 33, {colorTransform:{tint:0xC7DDC6, tintAmount:0.3}}); TweenMax.killTweensOf(this); The tween continues and works, but shouldn't it be killed? And I've noticed there is no complete parameter. Isn't there suppose to be? This does stop the tween: TweenMax.from(this, 33, {colorTransform:{tint:0xC7DDC6, tintAmount:0.3}}); TweenMax.killAll(true); I want to stop all and complete all tweens of an object before assigning another tween to it. So something likes this: TweenMax.killTweensOf(this); TweenMax.from(this, 33, {colorTransform:{tint:0xC7DDC6, tintAmount:0.3}}); And I want the object to complete during the kill. Thanks! -
Hi, I am trying to kill the common tween assigned to two movieclips TweenLite.to([obj1, obj2], 1, { y: 10, onComplete: smile } ); If I do something like TweenLite.killTweensOf(obj1); TweenLite.killTweensOf(obj2); the onComplete function continue to exhist, but why? I am doing something wrong for sure...
