Downside to running a timeline for 24/hrs?

[DennisSmolek]

I'm doing work on kiosk applications that have content that needs to change on a schedule. Think breakfast in the morning, lunch around noon, and after 5 dinner. 

 

We use GSAP on a bunch of other pieces and part of me wondered if there would be considerable issues with having a timeline run all day. 

 

I figure we use .addCallback() to fire a function at whatever time we want. 

 

The only other way is to do a setInterval() and have it check for registered callbacks in a time frame, both seem like they could have memory issues but the GSAP has a much nicer API...

[Carl]

Hi and welcome to the GreenSock forums,

 

I can't say I've tested a 24hr timeline but I have no reason to think you would have any issues using one for that type of scheduling.

 

We also have TweenLite.delayedCall() which is basically a much more reliable version of setInterval and it runs of TweenLite's ticker so all calls are perfectly synchronized with any other scheduled animations. 

 

[docs id=js.TweenLite.delayedCall()" linkText="delayedCall docs]

[DennisSmolek]

Awesome, thank you for the reply! For some reason I didn't get notified. 

 

I'm going to try it out and I'll post my results for sure.