Databases
StackOverflow2013
Postsdbo
PORadio buttons vs checkboxes for true/false/null options
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORadio buttons vs checkboxes for true/false/null options
    primarykey
    data
    text
    <p>I'm designing a generic survey engine and I've ran into some UI design related difficulties.</p> <p>I've decided that all survey elements that support multiple choices will invariably use combobox control. I think this is a good practice and Microsoft design guidelines promote this practice as well.</p> <p>However, I don't want to use comboboxes for Yes/No choices. These also need to support indeterminate state if the user doesn't select anything. My first choice was using two radio buttons which would read "Yes" and "No", but the problem with radio buttons is that they can't be deselected once selected (unless I break design guidelines and make radio buttons uncheck themselves upon another click). Alternatively, I could present the third option which would read "Unknown" or better yet, a small button which would remove any selection.</p> <p>The problem with using checkboxes is the way they handle indeterminate state. Most end users who will be using this software won't be very computer savvy and I don't expect them to realize that the small square in checkboxes representing indeterminate state DOES NOT in fact mean that the selection is positive. Check mark and square are probably the same to many users.</p> <p>To summarize:</p> <p>For YES/NO/NOT SELECTED types of items, should I use:</p> <ol> <li>Radio button with three choices reading "Yes", "No", "Unknown".</li> <li>Radio buttons which can be deselected by clicking.</li> <li>Radio buttons which can be deselected by clicking a small X button</li> <li>Checkboxes and hope that users will realize what indeterminate state is</li> </ol> <p>Thanks</p> <p><strong>UPDATE:</strong></p> <p>Alright, thanks to everyone who participated.</p> <p>I've opted for option #3 (Radio buttons which can be deselected by clicking a small X button), except that I use linkbuttons instead of buttons. I also provide a tooltip on the linkbutton in case the user isn't aware of its meaning.</p> <p>It looks like this:</p> <p><img src="https://i.stack.imgur.com/ZG7CE.jpg" alt="enter image description here"></p> <p>I'm pretty happy with this. Thanks again.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USVex
    1. USVex
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORadio buttons vs checkboxes for true/false/null options
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORadio buttons vs checkboxes for true/false/null options
      1. USMiserable Variable
      1. VTFavorite
    3. VO
      singulars
      1. PORadio buttons vs checkboxes for true/false/null options
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAs user, I vote for option 1, using Add Comment feature not mentioned in your list.
      singulars
      1. PORadio buttons vs checkboxes for true/false/null options
      1. USAlex F
    2. CO@Vex: you're making a bad decision with that "x" button. Nobody will know what that does. Stick with a standard way of doing things -- don't invent a new way to represent a third choice. Yes, they can hover over the "x" for a tooltip. but why make them do that when using a third radio button is completely obvious? Also, don't accept an answer so quickly -- you've given the community only one hour on a weekend to respond. Don't be so hasty. Give people a chance to give some quality answers.
      singulars
      1. PORadio buttons vs checkboxes for true/false/null options
      1. USBryan Oakley
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload