ticker wake issue

[erikb]

Ran into an issue this morning with the TweenMax.ticker.addEventListener.

 

Let me explain what I am doing and why it was a problem.

I was adding a tick event listener to a controller object which will send out diffs from a model to views.

(granted, this is not the primary use of your library, but as I use your library already, why not use its RAF functionality?)

 

Problem was that the initial diff object was being sent immediately, even before all of the components who need to listen for these events have been instantiated.

 

I traced the issue down to this line:

https://github.com/greensock/GreenSock-JS/blob/master/src/uncompressed/TweenMax.js#L5989

 

To work around the issue, I create a dummy tick listener and remove it right away:

    //wake up the tick engine so that our next call does not fire immediately
    var removeMeFunc = function() { console.trace( "wakey wakey"); };
    TweenMax.ticker.addEventListener('tick', removeMeFunc, this, false, 1 );
    TweenMax.ticker.removeEventListener('tick', removeMeFunc );

It would be nicer if there was an option I could set on the library to wake up the ticker without this workaround. 

 

Is there such an option or maybe a better approach?  Thanks.

 

See the Pen VaJGzo?editors=0010 by anon (@anon) on CodePen

[GreenSock]

An easier workaround would be to simply call TweenLite.ticker.wake() first (no need to add a dummy listener). But yes, I see what you mean and it should be fixed in the upcoming 1.18.5 release which you can preview [uncompressed] here: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/TweenMax-latest-beta.js

[erikb]

new library applied to my codepen here: 

See the Pen qZeWjO?editors=0010 by jedierikb (@jedierikb) on CodePen

[GreenSock]

Working well for you? 

[erikb]

Yes, in the pen it is working well and seems to be a good fix for that issue.  I have not been able to swap it into my larger project yet because... deadlines