LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

combo box displays value instead of label

Bill,

NI will chime in at some point, but so far the crowd here is proceeding exactly as an NI AE would likely do.

I can verify the undesirable behavior you are describing (I ignore all I/O-related errors, as you have suggested), but it's not clear from the thread so far that you've found a LabVIEW bug instead of a coding problem. It's definitely impossible to conclude bug/non-bug just by playing with the EXE, because the nondeterministic behavior you have described could be caused by race conditions arising on your block diagram that create different outcomes in IDE vs. EXE, machine 1 vs. machine 2, etc.

It would be possible to conclude bug/non-bug if we could examine the LabVIEW code. If that's not an option for privacy reasons (and if you can't make a stripped-down version to post), then I imagine the NI AE who joins the thread will have to e-mail you to get a look at the code privately.

Question: the UI seems much more complex that you suggest, unless you have done some really fancy control customizing. It seems as if the combo box is displayed in response to a button press, and that the resulting user choice is written back to a separate string indicator: three elements instead of just one listbox. Is that correct? Because of the apparent complexity, it's easy for an observer to suspect that a coding mistake is causing the problem.

My thoughts,
John
0 Kudos
Message 11 of 15
(933 Views)
Hi Bill,

When running the executable you posted earlier, I see the same behavior your describe. It is difficult to do much more without some sort of code to reproduce the behavior here. Is it possible for you to post your VI, including the block diagram so that more details of your program can be seen? If this is not possible, can you recreate the behavior in a VI that would be OK to post?

Failing that best advice I can give is to use a Text Ring, Menu Ring, or Enum to accomplish the same feel on your user interface.

Scott Y
NI
0 Kudos
Message 12 of 15
(923 Views)
OK, thanks for the help. I understand that you would have to see the source code - especially since the application is fairly complex, but I do have issues that prevent me from posting the source, and frankly, trying to make a non-proprietary version would take too much time since I have a workaround.

Combo boxes replaced with ring enums - problem appears solved.

Bill F
0 Kudos
Message 13 of 15
(911 Views)
I have noticed the same issue in fairly complex Exe where I am loading combo box with values from the database, where string==label, value== primary key. I never resolved it and it seemed to be fairly hard to reproduce so I let it go.
0 Kudos
Message 14 of 15
(892 Views)
I'm glad to see someone else has seen this same issue. I expect NI is probably aware they have an issue with combo boxes loaded at runtime. I am using enums instead of combo boxes and the problem goes away.

Bill F
0 Kudos
Message 15 of 15
(878 Views)