You can incorporate Menu Builder files into the existing source and
resource files of a non-MEAD application by #include
ing within the
application's source files.
The following table shows the six Menu Builder generated files that
should be incorporated into your application's source:
File |
Description |
menubuilder.mbld
|
XUL statements defining a saved menu structure and the
locations to where the source, resource and header files were generated to
create this menu structure within a Symbian
application. |
menubuilder.h
|
Specific command case statements.
#include this file within the
HandleCommandL function of your supporting application's AppUI
class, i.e. within its GUI .cpp file.
This is a user editable file that may contain code that
responds to menu item events. |
menubuilder.hrh
|
User entered custom menu Command variables defined as an
enumeration starting at 100.
#include this file within your application's GUI
.hrh and .rss files.
|
menubuildermenu.ra
|
Resource file representation of a designed menu i.e. an
implementation of r_menubuilder_menubar
#include this file within the body of your
application's .rss file.
|
menubuilderhkplain.ra
|
Resource file representation of the plain hotkeys for a
designed menu i.e. HOTKEY blocks
#include this file within the RESOURCE
HOTKEYS plain section of your application's .rss
file.
|
menubuilderhkctrl.ra
|
Resource file representation of the Ctrl hotkeys
for a designed menu i.e. HOTKEY blocks
#include this file within the RESOURCE
HOTKEYS control section of your application's .rss
file.
|
menubuilderhkshftctrl.ra
|
Resource file representation of the Shift+Ctrl
hotkeys for a designed menu i.e. HOTKEY blocks
#include this file within the RESOURCE
HOTKEYS shift_control section of a supporting application's
.rss file
|
|
When Menu Builder files are included in this way, the Menu Builder
can be used at any time to modify the menu of an application.