Menus and Resources (OLE)

Home | Overview | How Do I | Sample | Tutorial

This group of articles explains the use of menus and resources in MFC OLE document applications.

OLE visual editing places additional requirements on the menu and other resources provided by OLE document applications because there are a number of modes in which both container and server (component) applications can be started and used. For example, a full-server application can run in any of these three modes:

Stand-alone
In place, for editing an item within the context of a container
Open, for editing an item outside the context of its container, often in a separate window

This requires three separate menu layouts, one for each possible mode of the application. Accelerator tables are also necessary for each new mode. A container application may or may not support in-place activation; if it does, it needs a new menu structure and associated accelerator tables.

In-place activation requires that the container and server applications must negotiate for menu, toolbar, and status bar space. All resources must be designed with this in mind. The article Menus and Resources: Menu Merging covers this topic in detail.

Because of these issues, OLE document applications created with AppWizard can have up to four separate menus and accelerator table resources. These are used for the following reasons:

Resource name	Use
IDR_MAINFRAME	Used in an MDI application if no file is open, or in an SDI application regardless of open files. This is the standard menu used in non-OLE applications.
IDR_<project>TYPE	Used in an MDI application if files are open. Used when an application is running stand-alone. This is the standard menu used in non-OLE applications.
IDR_<project>TYPE_SRVR_IP	Used by the server or container when an object is open in place.
IDR_<project>TYPE_SRVR_EMB	Used by a server application if an object is opened without using in-place activation.

Each of these resource names represents a menu and, usually, an accelerator table. A similar scheme should be used in MFC applications that are not created with AppWizard.

The following articles discuss topics related to containers, servers, and the menu merging necessary to implement in-place activation: