Projects/Usability/HIG/Tabs Pages: Difference between revisions
(Access keys are set automatically, no need to mention them) |
(Added Implementation section) |
||
| Line 1: | Line 1: | ||
==Tabs and Pages in Dialogs== | ==Tabs and Pages in Dialogs== | ||
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. | 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. | ||
| Line 29: | Line 27: | ||
[[File:Paged_dialog.png]] | [[File:Paged_dialog.png]] | ||
=== See Also | == Implementation == | ||
* [http://api.kde.org/4.10-api/kdelibs-apidocs/kdeui/html/classKPageDialog.html KPageDialog]. | |||
* [http://api.kde.org/4.10-api/kdelibs-apidocs/kdeui/html/classKConfigDialog.html KConfigDialog] | |||
== See Also == | |||
* [[Projects/Usability/HIG/Dialogs|Dialogs]] | * [[Projects/Usability/HIG/Dialogs|Dialogs]] | ||
Revision as of 15:45, 27 June 2013
Tabs and Pages in Dialogs
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.
GOOD
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.
