Download
1 / 8
80 likes | 161 Views
MenuBar. Show the high-level structure of the AP Guidelines don’t put command buttons (or the like) on menubar don’t put a row of pushbuttons at the top of a window do you need the file menu? File as the first menu? provide the platform’s recommended menus if needed avoid one-item menu
E N D
MenuBar • Show the high-level structure of the AP • Guidelines • don’t put command buttons (or the like) on menubar • don’t put a row of pushbuttons at the top of a window • do you need the file menu? File as the first menu? • provide the platform’s recommended menus if needed • avoid one-item menu • options not fit for standard menus, add a top-level menus to the left of the help menu • help is the last item on every menu bar
MenuBars Guidelines • Match menu bars to the user’s work flow • Give critical or frequent tasks even weight • Use only one word for menu bar items • Use only one line for the menu bar • Do not gray out menu bar items • Menu bar items should always activate a drop-down menu
MenuBar Guidelines • Variations and Exceptions • window control menu, Apple’s “Apple” menu • Menubar layout • use three spaces between titles (one space in front the first/after the last) • Hide the menubar? • Put a “hide” option on the View menu and have the AP accept Escape to show the menubar again (or leave a little button at the lower right corner may be better)
Drop-down Menu • Good for accessing secondary tasks and selecting setting that affect the entire AP or window • bad for tasks that are more naturally handled using a mouse, to pick more than one option at a time • Guidelines • designate a keyboard shortcut for each option • the ellipsis indicator follows the label with no spaces • for dynamic menus, graying out inaccessible items is better than deleting/hiding them • with security levels, remove unavailable options
Drop-down Menu Guidelines • Menu option types • action, dialog box, settings, submenu, files, windows, graphics • Labels for menu options • following the standards for your environment • creating unambiguous labels • if it opens a window, match the window’s name • don’t repeat the menu title in the menu option • take advantage of the menus’ title • use parallel constructions: print a file, execute a program, etc • don’t abbreviate, use the singular • repeat labels only when uniqueness is not a virtue • capitalizing labels
Drop-down Menu Guidelines(II) • How to group options • organizing items into logical groups, then separating them into sets of >1, <5 items each • default options • usually the first (shown in bold in Windows 95/98) • depth and breadth • no more than two levels of cascading is suggested • as many drop-down menus at the top and the bottom
Pop-up Menu • Good for expert users who want shortcuts, accessing properties of selected objects • bad for options that appear nowhere else in the system • novice users who are unaware of pop-up menus • Guidelines • a cursor change can be used to indicate a pop-up exists • no titles (MS Windows) • orders of options: the object’s primary commands first, the transfer commands next, the properties last • no accelerators suggested • make sure the options also exist on the main menu or other more visible components
PopupMenu 方法 • 在 MDIForm 或 Form 物件上的目前滑鼠位置或指定的座標位置，顯示快顯功能表。 • object.PopupMenu menuname, flags, x, y, boldcommand Private Sub Form_MouseDown (Button As Integer, Shift As Integer, X As Single, Y As Single) If Button = 2 Then PopupMenu mnuFile End If End Sub
