05-28-2025 04:18 AM
@zou wrote:
Customize the ComboBox.
See attached.
Nice! And with a little tweak it should look like the System one (although it doesn't automatically update the looks)
09-09-2025 09:00 AM - edited 09-09-2025 09:01 AM
It seems that the combo box has a "bling spot" and unchecking the "Allow undefined values at run time" is not making the control bullet proof - here is a valid sequence how to force the combo box to yield undefined value by using just mouse clicks and keyboard presses during run time:
Because of this flaw I'm trying to avoid combo box controls.
BTW, the custom combo box control posted above also suffers from the same "blind spot" problem.
09-10-2025 10:07 AM
Empty string is a problem for ComboBox.
If config the ComboBox as following, when select the empty string from the pull down menu, it returns empty string instead of 2. See test VI in 2018.
09-10-2025 11:51 AM
Agree,
the empty string is the weak point of the LabView combo box .
Enum / Ring types can behave as combo boxes (and I use them for this purpose all the time), but they don't have the small arrow to remind the user to press there are select the record.
Luben Hristov
09-10-2025 06:27 PM - edited 09-10-2025 06:37 PM
Pulldown Enum & Ring attached.
09-10-2025 10:15 PM - edited 09-10-2025 10:19 PM
This modified control works better, but has another non critical flaw - if the text is too long it overlaps the arrow key.
I guess you used the standard enum & ring controls and customised them - you resized the arrows on the left side and moved them on the right side, the arrow down is overlapping the arrow up. Also the arrows stay on layer below the text field, so when you click on the arrow you technically click in the enum/ring text field, which naturally shows the pull down menu.
Another inconvenience is that it's a custom control (type cast) and you can't just drag/drop it from a common library location and use it. After dropped on the panel, first you need to break the typecast link to the original *.ctl file and then save it to a new file (failing to do so may result in entangled misbehaviour - by changing a file in one project you may affect other projects which use the same typeCast control in wrong way).