|
The class structure of the menu classes
in the Menus Catalog follows the rules used for all other classes
in the Windows Designer. This means that any changes that are made
should be done at the highest possible level in the hierarchy, so
that they filter down through the subclasses. This reduces the
number of times that a change has to be made, and makes maintenance
easier.
A recommended workflow for
defining Menu Pages and menu options is as follows:
|
·
|
Make one or more top level menu page classes, containing
definitions for as many as possible of the menu options (menu lines
and submenus) that will be used throughout the application. |
|
·
|
For each new Menu page, make a subclass (or sub-subclass if
necessary) of one of the top-level menu page classes. Unwanted menu
options inherited from the superclass can then be deleted from the
subclass, and any remaining menu options fine-tuned. |
|
