LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Ring Control displaying digital display when cleared on exit

A ring control with its strings cleared when the vi finishes execution, will display the digital display in its string , if the digital display was set to the non-zero item.
tested in win 2000 / XP systems, LabView 7.0
This is an issue in Labview 7, and not in previous versions of LabView
0 Kudos
Message 1 of 9
(2,994 Views)
When you clear the items, also set the value to '0'.

-Joe
0 Kudos
Message 2 of 9
(2,993 Views)
Instead of an empty array, set the "strings" property to an array of empty string constant. See attached.

Tim
0 Kudos
Message 3 of 9
(2,993 Views)

I vote BUG!

This used to work before LV7.

Ben


Ben Rayner
Certified LabVIEW Developer
www.DSAutomation.com

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 4 of 9
(2,993 Views)
Another thought.

In pre-LV7, I used to be able to set the selection for "-1". Since the user could only select non-negative values, any value other than "-1" would indicate a new value was selected.

Writing a "-1" now resluts in the display showing "<65535>" (-1). It used to show a blank selection.

To use the control in its current state, pre-LV7 code will have to be modified conciderably.

Let me try to explain why the previous behaviour was desirable.

If you want to distinguish between one of the items in the list being selected and nothing selected, writing a "-1" was great! The ring value could be passed to the selector of a case where the "-1" case would ignode the value read.

The default case could then be used to index out the selecti
on from the strings.

Simple, elegant, and worked great!

Now,
I have to append another string that indicates "no selection" and add extra code to trap this case. This gets even more complicated when the selections are populated by the code where the number of elements in the list can change.

I would prefer the previous behaviour be restored.

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 5 of 9
(2,993 Views)
Interesting that we use the (-1) case in our LV 7.0 programs. So I did a little digging. The default for menu rings is to be a U16 in which case what you're mentioning makes a lot of sense (it's an unsigned number after all). Click on the terminal in the block diagram and make it I16 and the (-1) now works. It's probably the easiest fix to just change them all to I16's (if you're using them in multiple sub-VI's you *did* make them typedef's so you only have to make one change, didn't you?).

Rob
0 Kudos
Message 6 of 9
(2,993 Views)
The real issue here is if you convert existing code written in LabView 6/6.1, it should work in the same way without having to worry about the little things, that makes you examine and rewrite some of the code
0 Kudos
Message 7 of 9
(2,993 Views)
Excelent point Rob!

The good news is the most recent app only uses 2 of them so it should be easy.

My reply above sounds a little desperate I must admit.

If I had known this was going to be "fixed", I never would have used it.

Quoting from Greg McKaskle from earlier today,
"
Why? Accepting the past is smart. Predicting the
future is really hard!
"

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 8 of 9
(2,993 Views)
I agree,

See my other reply to Rob.

It's a real drag when you find out a feature is really a bug that gets fixed without much mention in the release notes (yes I read them).

Ben
Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 9 of 9
(2,993 Views)