LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Slide control display bug

We are using some 2 slider slide controls with digital displays. As many users do, I like to use the TAB key to get from one input field to the next. When doing so one of the sliders disappears and the fill goes to some random place.

 

In the picture below I would expect one slider at 5 and the other at 9 and the fill in between.

Slider-tabbing-update-bug.png

 

I'm using LV2012 SP1. Don't have access to a newer LV version to test. Attached is the VI.

Just enter a value in one of the digital displays and use the TAB key to jump to the next input field to see the bug.

 

Any thoughts? Maybe fixed in a newer LV version?

 

0 Kudos
Message 1 of 8
(3,875 Views)

Still effed up (technical term) on LV14

0 Kudos
Message 2 of 8
(3,864 Views)

Thanks for testing in LV14. Still no reason to upgrade to LV2014 then Smiley Indifferent

0 Kudos
Message 3 of 8
(3,860 Views)

I can confirm the bug is still present at the 2014 version.

A small workaround would be to fill in the number, press enter and then double tab. Less than ideal, but you don't need the mouse.

0 Kudos
Message 4 of 8
(3,825 Views)

The workaround is not going to work when you have more elements on the FP. When confirming a data entry with Enter the slide will lose focus and tabbing will start from the first element on the FP, whatever that is.

 

0 Kudos
Message 5 of 8
(3,818 Views)

You are right.

If you are doing small increments/decrements another way would be to use the arrows up/down and then press tab. This doesn't make the bug appear.

You can also enter a number and then up-down with the arrow keys and then tab. I know it's not optimal but the tab position stays where it was. 

0 Kudos
Message 6 of 8
(3,807 Views)

Thanks for the idea, but users will not like that.

What we would need is to force a redraw. One option is to "disable & gray out" the slide and immediately enable it again when a tab key is detected. Seems to work, but also not an ideal solution/workaround.

 

 

0 Kudos
Message 7 of 8
(3,789 Views)

Bug still present in LV2020...

 

Another workaround that seems to work:

Slide bug workaround.png

0 Kudos
Message 8 of 8
(1,927 Views)