NI Home
Cart Cart | Help
Hello Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI
You are here: 
NI Home > NI Developer Zone > NI Discussion Forums


Announcements
The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!
fabric

System Controls: Change default boolean from Radio Button to Checkbox

Status: New
by Active Participant fabric on ‎06-08-2012 03:10 AM

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! :smileywink: 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.

Comments
by Active Participant Mads on ‎06-11-2012 06:13 AM

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.

by Active Participant fabric on ‎06-11-2012 07:31 AM

"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! ;-)

by Active Participant P@Anand on ‎06-11-2012 08:11 AM

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).

Latest LabVIEW Idea Exchange Blog Posts
About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Idea Statuses
Top Kudoed Authors
User Kudos Count
127
79
68
62
55
By using this web site, you accept the Terms of Use for this web site. Please read these Terms of Use carefully before using any part of this site. Please go here for information on ni.com's copyright infringement policy.
My Profile | Privacy | Legal | Contact NI © 2011 National Instruments Corporation. All rights reserved.    |    E-Mail this Page E-Mail this Page