Thank you again for your answers. First, I would like to make it clear - the only point in the VI I posted was to show the problem. I'm not using this construction anywhere and I don't plan to. Now, to the tab issue - We've now managed to identify the main problem in that program - refreshing arrays of rings 10 times a second takes a lot of resources when they're partially visible. We've changed that and now it's working fine. However, this doesn't change the fact that this problem also happened when these arrays were on non-visible pages of the tab control and would only go away when the arrays were completely moved off the screen. Just to show some numbers - I created a new tab control with two pages. In the first page I put the "problem" screen (which takes 0% when alone on the screen) and in the second I put two of these arrays (which took 10%). If the arrays are put near the tab and the first page is selected, the usage is 10%. However, putting the arrays into the second page causes the usage to go to 70% when displaying the first page, which originally took 0%. This causes me to suspect that there is something going on with the tab control. If anyone knows, please... BTW, I'm not sure how important this is, but I was told this program was converted from LV RT 6.1, where it was said to have worked fine. One last question - Greg, your answer was great, but according to what you say, shouldn't the frame rate have been lower for the "just grayed" array than for the "neither" one?
