Jump to content
GreenSock

Search In
  • More options...
Find results that contain...
Find results in...

Edify Technologies

BusinessGreen
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

3 Newbie

About Edify Technologies

  • Rank
    Newbie
  1. @ZachSaucier I just noticed your handling of the kill button by first assigning the tween to a variable tween = tl.tweenFromTo('start', 'end') and then killing it with tween.kill()... which is probably generally a better solution than my killAll() and trying exclude the timeline. Thanks for the quick replies!
  2. Thanks for the replies. That makes sense how you described it. Basically with tweenFromTo, a Tween is spun off of the Timeline. Based on that description, I would expect TweenMax.killAll() to solve my problem...and it does! Though, another unexpected behavior is after killing the tween with TweenMax.killAll(false, true, true, false) (the last false is for timelines) I would expect to be able to run tweenFromTo again by clicking the Start button. +1 vote for renaming kill() to politelySayNo() and killAll() to nuke() 😁 https://codepen.io/sallf/pen/OJJgypR
  3. I'm experiencing an issue where I can't kill() a timeline that was started with tweenFromTo. I also don't seem to be able to pause() or check isActive(). Expected result is that clicking the Kill button in mid animation, would ... well, kill the animation. Any thoughts? Note, in the CodePen, if you remove { paused: true } so that the animation runs on load, the Kill button and Indicator light both work as expected. https://codepen.io/sallf/pen/XWWgJgJ
×