LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Comments/Questions re Touchpanel

Hello Stephen,
 
the two loops have to be two while loops, since the application must be a multithreaded one.
Either one of the keyboards will produce the bug I'm talking about: the software keyboard as well as a hardware USB keyboard
0 Kudos
Message 11 of 14
(725 Views)

Hi AnthonV,

I can try to reproduce this here to see if a corrective action report needs to be filed.  Could you upload a VI that can demonstrate this error?  Thanks.

 

Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 12 of 14
(712 Views)
Hi Stijn,
Do you have any delay in those while loops?  If you have two untimed while loops (loops with no delay in them to set their execution speed), then they will run as fast as possible, eating up all of the available resources.  It could be that the controls are not responsive because the while loops have totally killed the processor.  Try putting a millisecond wait function inside them and see if you get the same behavior.  You should see a difference even if you just delay by 1 millisecond.
 
Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 13 of 14
(695 Views)

Hi Stephen,

for user interfaces I always use an event node in polling mode, for instance poll every 100ms

for background loops on windows targets (eg non RT targets) I use a wait in the loop. For RT Targets it is a wait until next multiple.

I am aware of processor starvation if you speed up loops, so I try to be as gentle as possible with all my timers, so this is not an issue in my bugpost.

best regards,

Stijn

0 Kudos
Message 14 of 14
(683 Views)