< Projects | Usability | HIGRevision as of 05:54, 27 May 2015 by Htietze (talk | contribs) (→Appearance)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) List View A list view is basically used to show some items. It offers orientation thereby and allows navigation without the need of other controls. Additionally, a list view may be used for single selection (users select one item from a list of mutually exclusive values) or multiple selection (selections in combination with the Shift key or Control key). However, because there is no common visual clue whether a list box’ mode is single or multiple and since other controls are more efficient for single selection, a list box should be used for single selection only. Guidelines Is this the right control Prefer a list view to show items that belong together and in case of sufficient space. Use the list view for selection if it is easy for users to know which items are checked at any given time, for one or more of these reasons: There are no more than twice the number of options then are visible at a time The options are well-known (for example months of a year or days of a week) Usually the selected options are close to each other in the list Do not provide extended multiple selection with Shift+Click or Ctrl+Click to select groups of contiguous or non-adjacent values, respectively. Instead, use the dual-list pattern if multiple items have to be selected, because it allows users to easily see which items are selected at any point, without having to scroll through the available options, and it can be used with only the mouse. (Once the list view is being revised this guideline is subject of change.) Behavior Do not have blank list items; use meta-options, e.g. (None) instead. Place options that represent general options (e.g. All, None) at the beginning of the list. Sort list items in a logical order. Make sure sorting fits translation. For lists with more than one column view, show headers and enable sorting by clicking the header. Show sort order in header. Appearance Alternate row color (use theme settings). Use different keys (e.g. page up/down) when more lists should be accessible. Make the list control large enough that it can show at least four items at a time without scrolling. If the list appears in a dialog or utility window, consider making the window and the list within it resizeable so that the user can choose how many list items are visible at a time without scrolling. Each time the user opens this dialog, set its dimensions to those that the user last resized it to. If activating a choice affects the appearance or the enabled state of other controls, place them next to the list view. If certain controls in a dialog are only relevant if a certain item is selected (i.e. they are dependent controls), disable them instead of hiding. Label the list view with a descriptive caption to the top left (cf. alignment). Create a buddy relation so access keys are assigned. End each label with a colon. Use sentence style capitalization for list view items. Implementation QListView, for single-column lists. QTreeView, for multi-column lists. Be sure to set the rootIsDecorated property to false if the items in your list do not have children. Retrieved from "https://techbase.kde.org/index.php?title=Projects/Usability/HIG/ListView&oldid=84900" Categories: UsabilityBehaviorEditing and ManipulationSelectionViewing and NavigationComplex views Content is available under Creative Commons License SA 4.0 unless otherwise noted.