Why are LabView Graphics so sloooooow?

[DNicholls]

Why does it take so long to load an application onto a PC even if it is only a single panel with a few dials and gauges.

And then after it is loaded, if I click a button with a mouse I'm not really sure if it has registered the action.

I have built applications of similar graphical complexity in either Delphi or Visual C and they load and run much much faster than a typical LabView app.

It sometimes seems that unless I have a CRAY sitting in my Lab the application is never going to start!

Anyone got any suggestion to speed it up?

[wiebe@CARYA]

Hi,

Here are some ideas. Without seeing your application, it's the best I can
do...

If your UI/MMI/CHI is reacting slow, you might need to put a Wait (ms) in
your while loop(s). If you don't, the loops take 100% processor time, and
there is no time to handle the UI properly.

The only reason (I can think of) why loading might be slow, is that you have
large default values.

Overlapping controls or indicators dramatically slow down the updating.

Boolean array, esp. 2d, are just slow.

Regards,

Wiebe.

"DNicholls" wrote in message
news:5065000000080000003C680000-1031838699000@exchange.ni.com...
> Why does it take so long to load an application onto a PC even if it
> is only a single panel with a few dials and gauges.
>
> And then after it is loaded,
if I click a button with a mouse I'm not
> really sure if it has registered the action.
>
> I have built applications of similar graphical complexity in either
> Delphi or Visual C and they load and run much much faster than a
> typical LabView app.
>
> It sometimes seems that unless I have a CRAY sitting in my Lab the
> application is never going to start!
>
> Anyone got any suggestion to speed it up?

[Greg_McKaskle2]

>>Anyone got any suggestion to speed it up?

If you are using a recent version of LV and using the 3D controls, they
use a rendering engine to draw the graphics smoothly at any size. If
you run them at 8 bit color they have to dither and look bad and draw
really slow. They run better at 16 bit color and best at 24 bit color.

A VI will take longer to load if it hasn't been saved for the platform
and version you are running on. If LV asks you to save on exit, then
that means the load included a compile as well.

The suggestion of placing a wait of 50ms or so in the loops will make
things much more responsive as otherwise you are checking the buttons
~20,000,000 times per second.

If you want more specific feedback, please describe the problem i
n more
detail or give access to the panel/VI.

Greg McKaskle