[Contents] [Index] [Next] [Previous]

File Menu


Description

The common File Menu contents are described as follows. Note that you should only include those functions actually supported by your application. If the label File is not appropriate to the context of your application, you can choose a different, more appropriate label. The File Menu can contain a TearOffButton. The illustration on this reference page shows a File Menu.

New
Must create a new file. The New operation must clear existing data from the client area. If completion of the operation will obliterate current changes to the file, you must display a DialogBox, asking the user about saving changes. This action must have the mnemonic N.
Open...
Must open an existing file. The Open operation must prompt the user for the name of the file with a DialogBox. The title bar should be updated with the name of the newly opened file. If completion of the operation will obliterate current changes to the file, you must display a DialogBox, asking the user about saving changes. This DialogBox should be displayed after the user selects a new file. This action must have the mnemonic O. Must save the currently opened file without removing the existing contents of the client area. If the currently opened file has no name, Save must prompt for a filename with a DialogBox. This action must have the mnemonic S.
Save As...
Must save the currently opened file under a new name without removing the existing contents of the client area. The Save As operation must prompt for the name of the file with a DialogBox. If the user tries to save the new file under an existing name, Save As must alert the user with a DialogBox of a possible loss of data. This action must have the mnemonic A. Must schedule a file for printing. If your application requires specific printing information before printing, the operation must first request that information with a DialogBox, and the entry title must be followed by an ellipsis. Printing information can also be specified for the application in the Options Menu. This action must have the mnemonic P.
Close
Can be supplied in applications that have multiple independent primary windows. This action must not be supplied in applications with a single primary window or multiple dependent primary windows. This action must only close the current primary window and its associated secondary windows; that is, the window family. This action must have the mnemonic C. You can include this action even though it is similar to the Close action in the window Menu. This ensures that users have a way to close the primary window even if they are not running a compliant window manager. Applications should prompt the user to save any unsaved changes if the action would cause loss of data.
Exit
Must end the current application and all windows associated with it. This action is equivalent to closing all primary windows of the application. If completion of the operation will obliterate current changes to the file, you must display a DialogBox, asking the user about saving changes. This action must have the mnemonic X. You should include this action even though it is similar to the Close action in the window Menu. This ensures that users have a way to end the application even if they are not running a compliant window manager. Applications should prompt the user to save any unsaved changes if the action would cause loss of data. If your application does not have a File Menu, put Exit at the end of the first Pulldown Menu.

Illustration

Related Information

See Application Design Principles for more information on the MenuBar system and for general information about Menu design.