Use such elements only when essential to the icon's meaning. Choose a more abstract or symbolic approach when the UI element is neither common, evident, nor unique.ĭon't overuse common elements like documents, folders, arrows, and the magnifying glass. With icons, there are a number of design points to avoid:ĭon't use icons that signify UI elements except when appropriate. Simplification: reduce the icon to its core meaning - get the theme across with just the necessary element(s) and no frills.Ĭontext: consider all aspects of an icon's role during concept development, which is crucial when deciding which elements constitute the icon's core metaphor.
Crucial icon design points center around clarity, simplification, and context.Ĭlarity: focus on the core metaphor that gives an icon its meaning and individuality. Visual Studio uses modern-style icons, which have clean geometry and a 50/50 balance of positive/negative (light/dark), and use direct, understandable metaphors. Used to indicate whether an operation is allowed using the mouse, where an object may be dropped, and so on. Used in progress indicators, status bars, and operation dialogs.Ĭursors. Use infrequently and only when necessary to illustrate a difficult concept or gain the user's attention (alert, warning).Īnimated images.
Images that appear in dialogs or wizards, either as descriptive graphics or message indicators. Images used in the preview area of a dialog, such as the New Project dialog.ĭialog images. Consult Menus and Commands for Visual Studio to see whether your command should get an icon. While images are used in the menu system, you should not create an icon for every command.
0 kommentar(er)
