Does the texture cache need to update if only dynamic properties were changed (opacity / transforms)

[fschutt]

• If I animate properties, I already skip the scene builder (because nothing has changed in the scene), but can I also skip calling renderer.update()?
• How are transforms handled internally - can I just add a transform to any node (so that I don't have to rebuild the display list if a user decides to animate a random node) or would that incur a performance hit?
• Is it possible to bind a dynamic color property to a gradient?

[kvark]

If I animate properties, I already skip the scene builder (because nothing has changed in the scene), but can I also skip calling renderer.update()?

There is scene building, and there is frame building following that. Both occur in "render backend". Calling update is necessary to receive that rebuilt Frame, even if the backend skipped the scene building.

How are transforms handled internally - can I just add a transform to any node (so that I don't have to rebuild the display list if a user decides to animate a random node) or would that incur a performance hit?

Good question! I'm not seeing any sources of overhead associated to this. @gw3583 do you recall any?

Is it possible to bind a dynamic color property to a gradient?

If not, you can make a PR to do this. I expect this to be straightforward.