|
|||||||||||||
Hi,
i'm using the german version of LV. Maybe some names are "like a decription" because i don't know the english
names corresponding to my indicators.
I'm using a combination field of strings and create the content using a propertie node with "StringsAndValues".
Elsewhere i'm using a propertie node with "Value" to know what selection the user made.
The normal way to ceate an indicator is right click, create indicator. But in this case the indicator has the same style
of the element "QueryCode" and doesn't show the value -> it shows the String part. The only way to get an indicator that
shows the value is by using the context menu.
Please change that! Whenever a propertie node with "Value" is choosen, right click -> create indicator should create an
indicator that shows the value and not the string or whatever.
> the indicator has the same style of the element "QueryCode" and doesn't show the value -> it shows the String part.
But the "string part" IS the value. The control you have there is a combo box, which is a string. That's the data type it has. Other than the string, it also has some additional strings, but they are NOT part of the value that comes out of the control. They are kept inside the control.
You are correct that creating an indicator from the Value property creates a control of the same style and with the same properties as the original control, but whether it should do that or not is debatable.
I think I actually agree with you in principle, but not because of the example you gave. Where it would be more relevant is if you have more complex controls. Creating a copy of the existing control by dragging it is a lot easier than creating a "clean" copy manually, so that's an argument for implementing your suggestion.
That said, I don't think I care enough to have NI do work on this.
>But the "string part" IS the value.
For me "READ_TYPE" is the string and "R" is the value (also if they are both strings).
Do i understand this wrong?
But the properties node "String[]" reads the strings as an array and the array contain "READ_TYPE" etc.
Otherwise the properties node with "StringAndValues[]" makes in this order no sense.
> For me "READ_TYPE" is the string and "R" is the value (also if they are both strings).
> Do i understand this wrong?
No, you understood this correctly. I didn't look closely enough at your original screenshot.
The problem is that you're using a combo box, which can have two strings, one for the value and one for display. In this case, "T" is the actual value, but the combo box control displays "READ_TYPE" when you select that value. It's interesting to note that the combo box indicator will display a specific element whether you write the value or the display string of the element into it.
I personally never use combo boxes. I use ring controls which have a numeric value, so I never run into this specific issue. Of course you can do this simply by dropping a string indicator and wiring it up to the value property.
You must be a registered user to add a comment here. If you've already registered, please log in. If you haven't registered yet, please register and log in.
Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
My Profile | Privacy |
Legal |
Contact NI
© 2011 National Instruments Corporation. All rights reserved. | E-Mail this Page
|
||

E-Mail this Page