LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
fabric

System Controls: Change default boolean from Radio Button to Checkbox

Status: New

I like system controls. 

 

In fact, if the system control set could be augmented to include cluster/array frames, graphs and some decent boolean indicators, then I would probably create an idea to ditch the modern controls entirely! Smiley Wink But I digress...

 

One very odd thing that happens when you set the system control set as your default is that every time you create a boolean control/indicator from the BD, you get a radio button! That's never what I want!! Are there any use cases where it makes sense to create a single radio button from an existing BD terminal or wire?? I'm guessing that the radio button is replaced with another control in 99% of cases.

 

I propose that the default boolean be changed to a checkbox.

 

This is obviously not going to satisfy all use cases but a checkbox makes much more sense than a radio button:

  • It makes sense as a "single entity"... the radio button does not.
  • It is just as compact. (Good for placing inside clusters, etc)
  • It may not be very intuitive as an indicator, but neither are any of the other system booleans!

 

This is a small but significant improvement that could surely be made very easily.

 

 

This has been mentioned before as an example within this idea, but I think it deserves to be evaluated on its own.

3 Comments
Mads
Active Participant

I've also found this rather strange. A checkbox would be an improvement, but I think a button would be even better. 90% of the time when I'm creating a boolean from the diagram I really want a button.

fabric
Active Participant

"A checkbox would be an improvement, but I think a button would be even better."

 

Yes - there are some good arguments for making a button the default too, but there are also some issues with that (at least with the existing offering of buttons). For me buttons seem less natural when representing data in clusters, classes, etc...

 

But either way, the radio button should go! 😉

P@Anand
Trusted Enthusiast

Yes I agree with Mads. I always use the system button and check box very least so it would be better if the default boolean control is a button (Easy to use in latching condition where you cannot use check boxes).

-----

The best solution is the one you find it by yourself