Gms-keep-compiled-resource is true in the current Global Settings object, GMS also deletes the compiled resource, if any.When you start G2, and
Gms-initiate-automatically is true in the current Global Settings object, GMS does the following.
Gms-initiate-automatically is false, and you start G2, GMS does nothing. The actions listed then occur only in response to explicit GMS API calls and/or choices in the G2 menus of GMS objects. The rest of this section describes those calls and choices, and their various effects.
You can use G2 menu choices and/or GMS API calls to compile any or all menu specifications. The API call to compile menus is:
gms-compile
(specs: item-or-value, window: class g2-window, build?: truth-value)
To compile a single menu specification:
Choose compile tree from the G2 menu of the menu specification's root template.
Call gms-compile giving the menu specification's root template as the value of specs.
To compile several menu specifications:
gms-compile giving the item list as the value of specs.
To compile all menu specifications:
Choose compile all from the G2 menu of any menu specification's root template.
Call gms-compile giving specs the value true.
If you call
gms-compile giving build? the value true, GMS automatically builds menus for the window designated by window after compilation is complete. You can also ask for menu building explicitly.
To build menus for a window:
gms-create-menu -> handle: integer
gms-compile to compile all menu specifications.
To delete all menu instances for a window:
gms-delete-menu -> success?: truth-value
gms-delete-menu:
true.
gms-delete-menu:
false.