Difference between revisions of "Projects/Usability/HIG/Tabs Pages"

< Projects‎ | Usability‎ | HIG
Jump to: navigation, search
(Paged Dialogs: New screenshot)
(Access keys are set automatically, no need to mention them)
Line 28: Line 28:
  
 
[[File:Paged_dialog.png]]
 
[[File:Paged_dialog.png]]
 
===Accessibility===
 
Do not assign accelerator keys to tab and paged dialog labels. Assign an access key to every other control on each page, however.
 
  
 
=== See Also ===
 
=== See Also ===
 
* [[Projects/Usability/HIG/Dialogs|Dialogs]]
 
* [[Projects/Usability/HIG/Dialogs|Dialogs]]

Revision as of 18:22, 19 June 2013

Contents

Tabs and Pages in Dialogs

General Guidelines

If a control affects only one tab or page in the dialog, place it on that tab/page. If it affects every tab/page in the dialog, place it outside, for example beside the window's OK and Cancel buttons.

Make sure changes on one tab will not change options on another tab.

Tabbed Dialogs

When to Use

Use tabbed dialogs when you have a limited number of tabs (max. 6). If you cannot see all the tabs without scrolling or splitting them into multiple rows, you are probably using too many and should use a paged dialog instead.

Tabs good.png GOOD

Tabs bad.png BAD

Paged Dialogs

When to Use

Always use paged dialogs for configuration dialogs - assuming that there is more than one section of options to be configured. For other dialogs, use paged dialogs if there are too many tabs to put them into a tabbed dialog.

Paged dialog.png

See Also


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