![]() Organize them into groups of related pages.Make the Advanced page or its equivalent the last page.Make the General page or its equivalent the first page.Instead, access customization through options. Users are often confused by this separation. That is, don't have both an Options command and a Customize command. Don't separate options from customization.If the selected object is a collection of multiple discrete objects (such as a file folder), display the properties of the single grouped object instead of a multiple-object property sheet for the discrete objects.(See the respective control guidelines for using mixed-state values.) Where the property values differ, display the controls associated with those values using a mixed state. Display the common properties of all the selected objects.Set input focus on an object and press Alt+Enter.Select the Properties command for an object.Property inspectors use an immediate commit (properties are changed as soon as users make changes), so there is no need for OK, Cancel, and Apply buttons. Properties for the current selection (a single object or group of objects) are displayed in a modeless window pane or undocked window.Īll property window patterns except property inspectors use a delayed commit, meaning that changes take effect only when users click OK or Apply. Properties for an application are displayed in a modal dialog box. The effective properties for a single object are displayed in a modeless dialog box. Properties for multiple objects are displayed in a modeless dialog box. Properties for a single object are displayed in a modeless dialog box. Property windows have several usage patterns. How would you explain it? What language would you use? That's the language to use in your property pages. Pretend that you are explaining the property and why it is useful to a friend. Present properties in terms of user goals, not technology. Organize the property pages efficiently.Design pages for specific users, especially limited users (non-administrators).Present properties in terms of user goals, not technology.Make sure the properties are necessary.To ensure that your property windows are useful and usable, follow these steps: As a result, when users are faced with a task in a property window, they often don't know what to do. Too often, these properties are organized into tabs, but beyond that not designed for any particular tasks or users. Property windows often become a dumping ground for an odd assortment of low-level, technology-based settings. You can display the most frequently accessed properties in a property inspector, and the complete set in the property sheet. Property sheets and property inspectors aren't exclusive. Are users likely to view or change properties for several different objects at a time? If so, use a property inspector otherwise, use a property sheet. ![]() Are users likely to view or change properties frequently or over an extended period of time? If so, use a property inspector otherwise, use a property sheet.Is the content mostly an object's properties (its settings or attributes)? If not, use a standard dialog boxe or tabbed dialog box.Is the content solely an application's attributes? If so, use an About box.Is the content solely an application's options? If so, use an options dialog box.Does setting the properties require users to perform a fixed, non-trivial sequence of steps? If so, use a wizard or task flow instead.Note: Guidelines related to layout and tabs are presented in separate articles. Property windows are often associated with tabs (and vice versa), but tabs are not essential to property windows. Property windows are usually organized into pages, which are accessed through tabs. Unlike dialog boxes (other than options dialogs) and wizards, property windows typically support several tasks instead of a single task. An attribute of an object that users cannot directly change (such as a file's size and creation date).A setting that users can change (such as a file's name and read-only attribute).Options dialog box: used to view and change options for an application.Ī property for an object is either of the following:.Property inspector: used to view and change properties for an object or collection of objects in a pane.Property sheet: used to view and change properties for an object or collection of objects in a dialog box.Property window is the collective name for the following types of user interfaces (UIs): Much of the guidance still applies in principle, but the presentation and examples do not reflect our current design guidance. This design guide was created for Windows 7 and has not been updated for newer versions of Windows.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |