zero length tween in timeline firing immediately

[erikb]

Got snagged by having a zero duration tween in a timeline fire before it should.

 

Worked around it by setting a duration really close to zero.

 

Bug?  Thanks.

See the Pen reQyqz by jedierikb (@jedierikb) on CodePen

[GreenSock]

Nope, that's not a bug - zero-duration tweens render immediately by default. That's what most people find the most intuitive, otherwise if you set() something and then had a line of code right after that which depended on that set() having been applied, it wouldn't work. See what I mean? 

 

All you need to do is set immediateRender:false -OR- you can do a set() directly on the timeline instance because in that case, it can tell if you're scheduling it for later. the problem with your example was that you were creating an independent tween (outside the timeline) and when that's created, there's no way for it to know that you're planning to add that to a timeline in the future, and schedule it further out. The timeline set() convenience method has the benefit of knowing that, thus it'll set immediateRender:false for you (unless it's at the very beginning of the timeline). 

 

Make more sense now?