Projects/Usability/HIG/Tabs Pages: Difference between revisions

From KDE TechBase
< Projects‎ | Usability‎ | HIG
(HIG moved to community)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Tabs and Pages in Dialogs==
{{ Moved To Community | KDE_Visual_Design_Group/HIG/Tabs Pages }}
 
'''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.
 
[[File:Tabs_pages.png]]
 
===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.
 
===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 ===
* [[Projects/Usability/HIG/Dialogs|Dialogs]]

Latest revision as of 12:09, 4 August 2016

This page is now on the community wiki.