> 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, t
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 array
> Thank you all for your answers. They've been very helpful in
> understanding the problem. I understand that refreshing the screen is
> hard and I know that LV requires a lot of resources but still - we're
> talking about 10 FPS - that's not a fast refresh rate. In response to
> Shea's question, w
Thank you all for your answers. They've been very helpful in
understanding the problem. I understand that refreshing the screen is
hard and I know that LV requires a lot of resources but still - we're
talking about 10 FPS - that's not a fast refresh rate. In response to
Shea's question, we have a f
Hello tst,
Thank you for your inquiry regarding CPU usage when using an array
covered by a control. After running the VI I understand the problem
that you are having and this problem does exist in standard LabVIEW
7.0. It takes a lot of resources to update a front panel when
controls/indicators are
