Programmably select item from combobox (strings and values[]).

[Lugaro]

I tried use  property node "Value" of combobox, but it good for "strings[]", not "strings and values[]".

Task: change combo box in interface when input data from Python node.

[GerdW]

Hi Lugaro,

---

@Lugaro wrote:

I tried use  property node "Value" of combobox, but it good for "strings[]", not "strings and values[]".

---

What have you tried? (Mind to attach code? LV2017 preferred!)

Where did you fail?

What's wrong with using "strings[]"? Which "value" did you set?

Is there a typedefinition involved?

[Lugaro]

Now I cant give code.

Why not string[]: 

User must see in combo box "COM1: Serial USB" and "COM10: Virtual port". Combo box must return only "COM1" or "COM10".

So: STRING "COM1: Serial USB" , VALUE  "COM1".

Where I fail: 

If I make "value"  - "COM1: Serial USB" . Return combobox value is "COM1:". Need "COM1".

[GerdW]

Hi Lugaro,

first you should remove that glaring race condition in your code!

Reading the combobox in parallel to writing its properties will most likely give unexpected results...

[Tom_Powers]

The little arrow in the string output that you have circled is and indication that there is more data than it is showing.  Expand the box out to be as long as the one that has the info on it and you should see everything.

[paul_cardinale]

---

@GerdW wrote:

Hi Lugaro,

first you should remove that glaring race condition in your code!

Reading the combobox in parallel to writing its properties will most likely give unexpected results...

---

Oh it's worse than "most likely give unexpected results".  It can give 'expected results' most of the time, even for years; then for no "apparent" reason, start giving unexpected results.

[Tom_Powers]

To add into the what could go wrong in parallel code.  Every time you make a change, even a minor one, to your code it gets recompiled. The order which parallel items end up happening can be changed depending on the compile operation. Thus it is aways best to have explicit order of operation. 

A single frame sequence with all of the stuff that you expect to happen before the loops starts with something from it being wired to the edge of your main loop is how I handle this.  It does not have to be used in the main loop just wired up to it.

[paul_cardinale]

---

@Tom_Powers wrote:

To add into the what could go wrong in parallel code.  Every time you make a change, even a minor one, to your code it gets recompiled. The order which parallel items end up happening can be changed depending on the compile operation. Thus it is aways best to have explicit order of operation. 

A single frame sequence with all of the stuff that you expect to happen before the loops starts with something from it being wired to the edge of your main loop is how I handle this.  It does not have to be used in the main loop just wired up to it.

---

No, it's not "aways best to have explicit order of operation".  Rules that say 'Always this..'  or 'Never that...'  are brainless.  What's really best is to use your brain to figure out what to do instead of relying on some simplistic rule.

[FireFist-Redhawk]

---

@Lugaro wrote:

Why not string[]: 

User must see in combo box "COM1: Serial USB" and "COM10: Virtual port". Combo box must return only "COM1" or "COM10".

So: STRING "COM1: Serial USB" , VALUE  "COM1".

Where I fail: 

If I make "value"  - "COM1: Serial USB" . Return combobox value is "COM1:". Need "COM1".

---

The race condition is of course a glaring problem. There's also another thing I think... When using "Strings And Values []" property, the String is what you want to be displayed in the combo box and the Value is what the combo box actually outputs. If you also change the value of the combo box with a Value or Value Signaling property node or a local variable, it messes that all up by writing both the string and value. Whereas if the combo box value is chosen using the dropdown, the correct output will result ("3" in this case).

Spoiler

[Yamaeda]

---

@Lugaro wrote:

Now I cant give code.

Why not string[]: 

User must see in combo box "COM1: Serial USB" and "COM10: Virtual port". Combo box must return only "COM1" or "COM10".

So: STRING "COM1: Serial USB" , VALUE  "COM1".

Where I fail: 

If I make "value"  - "COM1: Serial USB" . Return combobox value is "COM1:". Need "COM1".

---

Why not just use Value with the long string and cut the string at colon?