Database Performance: Overhead associated with conditionally visible objects

[Jarvis]

How much overhead is associated with conditionally visible objects?

 

If I have a popover button or a slide control that is conditionally visible and the condition is such that this object is not visibly present, does the server have to evaluate for this condition anyway?

If nothing is being drawn or refreshed on the screen does this add weight to the file?

 

Put another way,  if the condition is such that the object is visible, does this take longer to load than if the object was not visible?

[David Jondreau]

It depends.

 

I wouldn't expect a difference for just a button object or slide control alone.

 

But if that object is displaying data, such as container, related, or unstored calculations, then you'll likely see a difference.

[Jarvis]

Thanks David,

 

I am trying to make this thing be kind of like a blank layout.

I don't want to unnecessarily clog the arteries but I don't mind a little performance degradation if there is some nutrition at the end of the road.

[Josh Ormond]

If I were you I would create a new file and test it. Throw a bunch of objects on a layout, conditional visibility setup...and see what happens.

 

Test them visible, and not.

 

Some of the performance is going to be based on the complexity of the formula. Since FM has to read it, and calculate it.