icg_cnunez
icg_cnunez's Achievements
0
Reputation
-
I have a DOM element that stores a TimelineLite Object in a data object. I reference this stored TimelineLite Object at a given time and call the kill() method on this object. From what I understand and desire, the kill() method will immediately stop the animations on the TimelineLite Object and release for garbage collection. I have several tweens and potentially timelines nested in the referred TimelineLite Object. I want them all to stop immediately even if currently tweening. They should stop right where they are. This is not what I am experiencing. Currently tweening animations/tweens continue to run until completion, and only then do animations stop (do not continue to run). Am I doing something wrong here? Should I be using a different method to accomplish the desired result? Should I be getting the nested tweens/timelines and then kill() those first? -
I understand. Yes, I would definitely vote for that functionality. Although, I am able to work with the current functionality as is. Again, it's just the convenience of it (using convenience methods the way I would like). I am working on my first applications of Greensock, and I already have a need for using repeat functionality in my tweens and nesting them inside a timeline. But like you said, I just had to create my TweenMax, and then add it to the timeline. Maybe one day there will be enough demand or need to add the convenience methods as a part of TimelineMax to use TweenMax.
-
Thank you. Any thoughts/plans for the future to make timeline convenience methods intelligently determine whether to use a TweenLite vs. TweenMax based on what's needed to achieve the special properties (basic/advanced) passed in the vars param of the tween? That would truly be a convenience method with complete flexibility. Just a thought on my part. It would be nice to have. Thanks again!
-
Do TimelineMax convenience methods only create TweenLite Classes, or can they create TweenMax Classes? I want to create TweenMax Objects, not TweenLite Objects. If I want to do this, will I have to use TimelineMax.add(TweenMax.convenienceMethod())?
-
Okay, thank you.
-
Here is the link: http://api.greensock.com/js/com/greensock/TimelineLite.html#add() It is the last example before the parameters are defined. It seemed to me that by using tl.add($elements, "stagger", staggerValue); I could bypass the position and/or align parameters. Is this not true?
-
Simple question regarding TimelineLite / TimelineMax .add() with Stagger: Is it necessary to do this: tl.add([tween, tween, tween], "+=5", "normal", "stagger", 5); // shown in documentation example or would you do this: tl.add([tween, tween, tween], "+=5, "normal", 5); // what I would expect to do
-
Oh yeah!!! This works perfectly!!!!! Thank you, Jack! I was loosing my mind over this since yesterday.
-
I have two TimelineMax objects: ------------------- THE CYCLE: TL1 repeats once with yoyo. TL2 repeats infinitely with yoyo. TL2 is initially set to paused. TL1 plays automatically, & onComplete plays TL2. TL2 has onRepeat to pause itself (TL2), and restart(true) TL1 (restart should respect TL1's delay). ------------------- INTENDED EFFECT: I want the infinitely repeating timeline, TL2, to play and pause at each repeat point of its animation, but this is not happening. Both timelines' playback are controlled by the other. If you look at my Codepen code, you will see that this is not working correctly, and I can't figure out what I'm doing wrong. http://codepen.io/icg-cnunez/pen/nDKoJ Any help much appreciated.
-
Okay, I get it now. The delay was included in the repeat in my scenario, because I set the delay on the nested tween, and I had set the repeat on timeline it was nested in. So the timeline was repeating its nested tween, which included the tween's delay.
-
That's great! Thanks for the trickery, Carl!
-
Yes, that is exactly what I needed. Thank you for clarifying how the timing with the delays work repeat and yoyo. I initially understood a delay to just apply to the start of the animation one time, and not be included in the repeating. But i see that is not the case. The delay is included in repeats.
-
ISSUE: Using delay with yoyo causes a timing issue that is strange to me. In other words, I don't understand why I am experiencing unexpected results. I will share a JSFIDDLE simplified example that replicates exactly the issue I am experiencing. This is what's happening: I have a delay of 1 and repeatDelay of 1 to continue same delay timing throughout the looping animation. Yoyo is set to true. I would expect there to be a consistent 1 second delay between each tween, but with yoyo in effect, after yoyo returns to the start of the animation, there is a 3 second delay, not a 1 second as repeatDelay defines. THE CODE: http://jsfiddle.net/icg_cnunez/bjBgF/4/ QUESTION: Why is this happening and how can I achieve the desired behavior with timing, where each delay (delay or repeatDelay) results in only 1 second between tweens throughout the entire animation? Any help much appreciated.
-
@ http://codepen.io/GreenSock/pen/agJkA Carl, thank you for the examples. I like this one, but is there an easy way to make it seamless using the example code you provided here. With this one, the last box has to fade out completely before the animation starts again, whereas all boxes after the first overlap fades. This would be great if the repeat (first box) would would overlap the last one's fade so the looping is seamless.
-
Thank you for your reply, Carl. A little more on what I'm trying to do: I am cycling through several elements where sequentially one element fades out and the following element fades in. This cycle needs to be a continuous loop. When I get some additional time, I will put together a test case in jsfiddle and share it.