Projects/Usability/HIG/Buttons: Difference between revisions

From KDE TechBase
< Projects‎ | Usability‎ | HIG
No edit summary
m (→‎Guidelines: typo--)
Line 4: Line 4:
* Use [[Projects/Usability/HIG/Capitalization|title style capitalization]] for the label.
* Use [[Projects/Usability/HIG/Capitalization|title style capitalization]] for the label.
* Buttons are not dynamic; their content or labels should not change depending on the context. [[Projects/Usability/HIG/Toggle_Buttons|Toggle buttons]] are a special case where a button has a state.
* Buttons are not dynamic; their content or labels should not change depending on the context. [[Projects/Usability/HIG/Toggle_Buttons|Toggle buttons]] are a special case where a button has a state.
* Don't initiate an action on right-click or double-click cause the user won't expect it.
* Do not initiate an action on right-click or double-click.
* Prefer using icons on buttons only for ok, apply, cancel like actions. Passive actions like e.g. those in the "System Settings => Application Appearance => Fonts" don't have icons. Don't overboard with icons.
* Prefer using icons on buttons only for OK, Apply or Cancel like actions. Passive actions like those in the "System Settings => Application Appearance => Fonts" do not have icons.

Revision as of 12:31, 27 June 2013

A button initiates an action when the user clicks it.

Guidelines

  • Use title style capitalization for the label.
  • Buttons are not dynamic; their content or labels should not change depending on the context. Toggle buttons are a special case where a button has a state.
  • Do not initiate an action on right-click or double-click.
  • Prefer using icons on buttons only for OK, Apply or Cancel like actions. Passive actions like those in the "System Settings => Application Appearance => Fonts" do not have icons.