Difference between revisions of "Projects/Usability/HIG/Check Box"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(How to use)
(Replace "Code snippets" with "Implementation")
(3 intermediate revisions by 2 users not shown)
Line 9: Line 9:
 
* Do not use a check box if the opposite is ambiguous.
 
* Do not use a check box if the opposite is ambiguous.
 
[[File:HIG_Checkbox1.png]]
 
[[File:HIG_Checkbox1.png]]
* For more than five options, use either a [[Projects/Usability/HIG/ListBox| list]] with multiple selection enabled or the [[dual-list pattern]].
+
* For more than five options, use either a [[Projects/Usability/HIG/ListBox| list]] with multiple selection enabled or the [[Projects/Usability/HIG/SOU_Workspace/Two_Lists | dual-list pattern]].
 
* Do not add line breaks. If necessary place an additional label below the check box.
 
* Do not add line breaks. If necessary place an additional label below the check box.
 
[[File:HIG_Checkbox2.png]]
 
[[File:HIG_Checkbox2.png]]
Line 15: Line 15:
 
[[File:HIG_Checkbox3.png]]
 
[[File:HIG_Checkbox3.png]]
 
* If certain controls in a configuration dialog are only relevant if a certain check box is checked (i.e. they are dependent controls), disable them instead of hiding them if that check box is unchecked.
 
* If certain controls in a configuration dialog are only relevant if a certain check box is checked (i.e. they are dependent controls), disable them instead of hiding them if that check box is unchecked.
 
+
* Do not use the selection to perform commands.
In discussion
+
 
+
* Do not use the selection to perform commands or to dynamically display other controls and windows.
+
 
[[File:HIG_Checkbox4.png]]
 
[[File:HIG_Checkbox4.png]]
  
Line 27: Line 24:
  
 
=== Appearance ===
 
=== Appearance ===
* Do not use sliding switches in Desktop applications. They only offer good user interaction on touch screens, so they should only be used in applications for [http://community.kde.org/Plasma| Plasma Active].
+
* Do not use sliding switches in Desktop applications. They only offer good user interaction on touch screens, so they should only be used in applications for [http://community.kde.org/Plasma/Active Plasma Active].
 
* Do not separate check box and label. Clicking on both the box and the label should toggle the option.
 
* Do not separate check box and label. Clicking on both the box and the label should toggle the option.
 
[[File:HIG_Checkbox5.png]]
 
[[File:HIG_Checkbox5.png]]
Line 36: Line 33:
 
=== Text ===
 
=== Text ===
 
* Label every check box or radio button.
 
* Label every check box or radio button.
* Assign a unique access key to each label.
 
 
* Do not use ending punctuation (neither dot nor colon).
 
* Do not use ending punctuation (neither dot nor colon).
== Code snippets ==
+
 
to be done
+
== Implementation ==
 +
[http://qt-project.org/doc/qt-4.8/qcheckbox.html QCheckBox]

Revision as of 14:26, 27 June 2013


Purpose

A check box is a control that permits the user to make multiple selections from a number of options. Check boxes are used to toggle an option on or off, or to select or deselect an item. Users make a decision between two clearly opposite choices (on (vs. off), apply (vs. don't apply), show (vs. hide). etc.).

Guidelines

How to use

  • Use check boxes for non-exclusive options that have clear alternatives. Mutually exclusive options should use a set of radio buttons or a combo box.
  • Do not use a check box if the opposite is ambiguous.

HIG Checkbox1.png

  • For more than five options, use either a list with multiple selection enabled or the dual-list pattern.
  • Do not add line breaks. If necessary place an additional label below the check box.

HIG Checkbox2.png

  • Checking a check box should always "enable" an option or change the state of an option to "on". Checking a negative or disabling option is a double negative and causes confusion and errors.

HIG Checkbox3.png

  • If certain controls in a configuration dialog are only relevant if a certain check box is checked (i.e. they are dependent controls), disable them instead of hiding them if that check box is unchecked.
  • Do not use the selection to perform commands.

HIG Checkbox4.png

Mixed state

  • Use the mixed state only to indicate that an option is set for some, but not all, child objects. Mixed state must not be used to represent a third state.
  • Users must not be able to set a mixed state directly.
  • Clicking a mixed state check box enables all child objects.

Appearance

  • Do not use sliding switches in Desktop applications. They only offer good user interaction on touch screens, so they should only be used in applications for Plasma Active.
  • Do not separate check box and label. Clicking on both the box and the label should toggle the option.

HIG Checkbox5.png

  • Align groups of check boxes vertically rather than horizontally, as this makes them easier to scan visually. Use horizontal or rectangular alignments only if they greatly improve the layout of the window.
  • Check box labels are in sentence style capitalization.
  • For layout directions, see label alignment: check boxes.

Text

  • Label every check box or radio button.
  • Do not use ending punctuation (neither dot nor colon).

Implementation

QCheckBox


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal