Are indicators updated on an inactive tab control page

[RoyA]

To decrease loop execution speed (increase acquisition speed) I have placed diagnostic displays on a seperate tab control page which is normally not the active page.  The thought is that speed will be increased as these displays would not be updated unless needed (screen I/O is normally time consumming).

Is this a viable method?

Roy

[aartjan]

It is not that those controls will not be updated, but the drawing of those controls on the screen that you save. This can definitely be very significant. It is also good programming praxis to hide unnecesary front panel elements.
Also keep in mind that the eye can only handle 10-20 updates a second, and even that is for most controls much too fast. Lowering the indicator update rate to, say, 5-10 times a second, can  already achieve  major CPU relief. depending on the kind of interfacing I would go to much slower updates still.  If you use big data sets, you should also try to prevent creating too many copies in memory.

[RoyA]

Thank you, Aart-Jan.  I should have been more specific.  I knew it was the screen draw that took time.  When I referred to 'update' I meant updating the screen image, not the value in the indicator itself.  I just wanted to make sure that placing these controls in the inactive page insured that there would be no screen activity related to them.  Before tab controls I had a 'Debug' Boolean that controled the visibility of such indicators, but it was messy to have all those property nodes cluttering up the block diagram.  Glad to have it confirmed that I can handle this just by placing them on a 'back page'.