combo box output items name instead values

[weitong]

I met a problem with combox application.

By selecting the combox item name, I wish to get the corresponding values. But always the combo box gives item name, even if I use its property node(value).

LV2012SP1

WT

[weitong]

Occasionaly, If I uncheck "Allow undefined values at run time"  under the combo box propeties "Edit Item" tab, then it output values instead of item names.  After this, with  "Allow undefined values at run time"  checked, it output values, too.  Strange behaviour!  

This is not always working.

WT

LV2012SP1

[weitong]

Attached please find the combox VI. Please take a look to check the problem.

WT

LV2012SP1

[billko]

What is the VI supposed to show?

[billko]

When you uncheck the box, did you actually define values for your control?

[weitong]

The VI (string2 and string3) is supposed to show the values which is defined in the item table.

I found the solution. To achieve this purpose, one have to use the Text.text property node to choose the item in the combo box. With a string given to the combo box, it doesn't work. This seems to be contrary to one's general thought.

[DrRob2020]

Dear all. There is a way to make it work with the text combo box, but it is a bit cumbersome. If we create a property node of strings and values, this outputs an array of bundles, which contains both the text and the items. We can then unpack the bundles and perform operations with them. I have attached a VI, that accepts both the array of bundles (named binning) and a property node:text.text (binning) which will look though the array of bundles and check if a desired text is there. It will then return the value.

Hope this helps

Robert

[altenbach]

It is not helpful to post a response to an 11 year old thread with a relatively dysfunctional VI that cannot run on its own.

• Autoindexing on a FOR loop (showing the conditional terminal) would be significantly simpler than a while loop randomly limited to 21 iterations. Can't the input array be larger?
• You can wire the stop condition direction to the comparison output. No need  for all these boolean constants.
• terminals assigned to connectors should reside on the toplevel diagram, not inside structurers.
• There is no terminal called "binning" or any property nodes. Did you really attach the correct VI?
• ...