Jump to content
GreenSock

Search the Community

Showing results for tags 'delays'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • GreenSock Forums
    • GSAP
    • Banner Animation
    • Jobs & Freelance
  • Flash / ActionScript Archive
    • GSAP (Flash)
    • Loading (Flash)
    • TransformManager (Flash)

Product Groups

  • Club GreenSock
  • TransformManager

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hey! So I have a timeline loop that should loop infinitely, each new timeline has a negative offset to keep the loop from having a gap at the beginning of each timeline I can achieve the desired effect by adding the same timeline with negative delay multiple times ( lots of timeline.add(anim(), "-=3") ) But for some reason today I can't wrap my brain around how to do this nicely? I have tried various things, negative repeatDelay, onComplete set time() / progress(), but none of them quite work. Something like 2 timelines and the second one loops forever sounds like the right way to do it? Please look at the codepen and all should be made clear, on each 'repeat' of the master timeline there is a gap Thank you in advance ? I'm so sure it's something really simple that I'm overlooking!?!
  2. I couldn't find this in the documentation, so I figured I should make a request here! Could TimelineMax be added the same funtionality as TweenMax where you can delay method calls? I realize it couldn't "reverse" the actions caused by those methods (unless a respective reversible callback method was supplied for each delayed callbacks... but nah!), but this would be very handy instead of using dummy [TimelineMax instance].to(...) calls, like the following: var animation:TimelineMax = new TimelineMax(); //Delay the next object's to be added to the displaylist later: animation.to( dummy, 1.5, {onComplete: addChild, onCompleteParams: [someSprite]} ); //INSTEAD, this would be nice! animation.delayedCall( 1.5, addChild, [someSprite] ); It would be SHORTER, sweeter, and ~loved~ by many I'm sure (me first!) Is there any internal complications that prevents this from being implemented?
×