[GSAP v2.1 immediateRender]

Thanks a lot for the super quick response and the clarification Jack! It's a lot clearer now.

 

8 minutes ago, GreenSock said:

Are you saying that the docs need to mention the way the paused state affects the default immediateRender on from()/fromTo()?  

 

Correct. I saw that you already updated the docs, so thanks for that as well

[GSAP v2.1 immediateRender]

I just started a new project and I installed the latest version of GSAP (v2.1.1). I read on the changelog of v2.1.0 that:

 

Quote

TimelineLite/Max.set() consistently has its immediateRender default to false now.

 

I was experimenting with a TimelineMax timeline that has various `.fromTo()` and `.from()` calls and it appears that `immediateRender` is also set to `false` on these functions as well (only when the timeline has `paused` set to `true` and I play it later on). I wanted to ask: Is this the expected behavior? If not, I guess something could be wrong with my setup. If yes, I think the documentation should be updated so that folks do not get confused. Right now the TimelineMax.from() documentation reads:

 

Quote

NOTE: By default, immediateRender is true in from() tweens, meaning that they immediately render their starting state regardless of any delay that is specified. You can override this behavior by passing immediateRender:false in the vars parameter so that it will wait to render until the tween actually begins.