SUBMITTED: Nested container cooking behavior

Not sure if this is a bug or a RFE, so I’ll put it here.

When you have an animated parameter at /container1, then all other containers inside /container1 also cook every frame. Is this necessary?
For example, just setting the display parameter of /container1 would change /container1/container* to cook. So if you have 100 containers inside, this quickly consumes ~2 ms, although you basically don’t change much/anything.

But also when animating panel[xywh] at the top level container, shouldn’t this just offset the whole container and not cause the children to cook?

Achim

Yeah, I just confirmed this. I would expect it not to cook if display or enable of a Panel Component was turned off, but it cooks every frame. Moving this thread to bugs…