From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

change user-interface priority

Hello LabVIEWERS ,

Does anyone of you know how to set/adjust the user-interface priority of a
LabVIEW program.
In an certain application I noticed a bad respons from LabVIEW towards the
user-interface
(it reacts only very slowly towards pushing a button or for instance
dragging the LabVIEW frontpanel)
although the processor utilisation is only a few percent. I don't want to
put delays in the code unneccesary.

I tried to lower the execution priority of LabVIEW but I don't see any
difference.

I use windows2000 as platform and LabVIEW 7.1 if that matters.

René Ramekers


0 Kudos
Message 1 of 3
(2,240 Views)

hi there

in almost all cases the reason for slow gui response is NOT the priority of the vi. there are a lot of reasons:

- (hidden) delays (e.g. reading from an interface using a timeout)
- lot of memory/disk access
- lot of data to show on the gui
- unneccessary repitions of function/vi calls
- (very) poor graphic hardware

do you use event based programming and a high level/low level architecture in your application?

i think best would be to post some code here, so we can have a look at it. like i said, there are a lot of possible reasons...

 

 

 

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
Message 2 of 3
(2,233 Views)
Thanks for you suggestions, but I already found it myself:
it appeared to be a DLL which was called very often ,
and this DLL was running in UI - thread. Changing it to "reentrant" did the
trick .

René Ramekers

"chrisger" <x@no.email> wrote in message
news:1156255808695-407091@exchange.ni.com...
> hi there
> in almost all cases the reason for slow gui response is NOT the priority
of the vi. there are a lot of reasons:
> - (hidden)&nbsp;delays (e.g. reading from an interface using a timeout)-
lot of memory/disk access- lot of data to show on the gui- unneccessary
repitions of function/vi calls - (very) poor graphic hardware
> do you use&nbsp;event based programming and a high level/low level
architecture in your application?
> i think best would be to post some code here, so we can have a look at it.
like i said, there are a lot of possible reasons...
> &nbsp;
> &nbsp;
> &nbsp;


0 Kudos
Message 3 of 3
(2,219 Views)