Menu Overview

Artigo
04/19/2010

4/19/2010

The menu bar in Windows Mobile Professional and Windows Mobile Classic is replaced with soft keys that access menus and define the ways in which they are displayed. For any application that has one or two menus and that is compiled against the Windows Mobile SDK, the menus are rendered as soft keys. Windows Mobile supports two soft keys, SK1 and SK2. SK1 is the left soft key and is usually used for the most common action for the application. SK2 is the right soft key and is usually used to display the rest of the applications commands on a menu that is displayed when SK2 is selected.

Note that beginning with Windows Mobile 6.5.3, soft keys are replaced by touchable tiles on Windows Mobile Professional phones. **

In Windows Mobile 6.5, all Microsoft applications use soft keys on Windows Mobile Professional, Windows Mobile Classic and Windows Mobile Standard. Support is provided for OEM–customized soft keys.

Shortcut menus appear when the user taps the stylus at a point on the screen and holds it down for a short period. When the stylus is held down in a position served by a shortcut menu, animated feedback around the point of the stylus signals that a shortcut menu is going to appear. The tap–and–hold gesture for displaying shortcut menus is recognized by using the SHRecognizeGesture function in the WM_LBUTTONDOWN message handler. The shortcut menu provides commands that are useful in the context of the object under the stylus. For example, common shortcut menu commands are Cut, Copy, Paste, and Refresh. The menu can be displayed from an existing menu resource, or constructed dynamically by using the Windows Management AppendMenu function. You can also dynamically add items to an existing menu resource. Dynamically adding items to the menu is slower than using a predefined resource. but is an option if you need to create such dynamic behavior.

If you want to customize file lists with your own menu options for specific file types, you can extend shortcut menus that appear in file lists in any application. For Windows Mobile, you can give users additional menu options when they tap and hold a .doc file in Word Mobile, or when they tap and hold a .jpg file in File Explorer Mobile.

A shortcut menu extension is implemented as a COM server component. You can use an abstraction interface exposed by the application that you are adding your component to. Your component gets application-specific information through this interface. The shell sets the application's abstraction interface to be the site of your component with a call to your implementation of IObjectWithSite::SetSite. When the user opens a menu containing your extension, the shell calls your implementation of IContextMenu::QueryContextMenu to show the new commands your extension makes available. When the user selects one of the new commands, the application calls SHInvokeContextMenuCommand, which in turn calls your implementation of IContextMenu::InvokeCommand. Your component gets a reference to the application abstraction interface by calling your implementation of IObjectWithSite::GetSite.

The following tables provide information about where you can extend the softkey menu and shortcut menus in the Windows Mobile device user interface. They also provide details about the abstraction interface to use, which header file to include, and the registration information you'll need to register a menu extension in each UI location.

The Location in User Interface column, can either be the Summary screen, which refers to the window that shows the existing list of files created by the application, or it can be the Main screen, which refers to the editable window that provides core application functionality. An example Windows Mobile would be the blank document that appears when you tap New on Excel Mobile ** summary screen.

You use the information contained in the Context and Class columns to register application shortcut menu extensions. For more information, see Registration Format for Application Shortcut Menu Extensions.