Menus - Texas Instruments TI-89 Developer's Manual

118
See section 11.4.2. Dialog Fields for a description of the individual fields and
their parameters. There are a few differences in defining a dialog box with the
resource compiler as noted in the following paragraphs.
DYNHEADER does not have a field for the text of the header. Instead, the
call-back is called with the DlgId parameter set to DB_GET_TITLE. The call-back
routine must return a pointer to the text to use for the title. DYNHEADERs are
only available in the resource compiler and cannot be added to dynamic menus
with the DialogAdd function.
HEDIT entries do not use the BufferOffset or FieldLength fields and so these
should be set to zero ( DisplayLength must still be provided).
MENU (TOOLBOX can be used also) and POPUP require the name of a menu
or pop-up that is defined elsewhere in the resource file.
11.5.2.

MENUs

MENU MenuName, Flags, MaxHeight, MaxWidth {
Text1, TOP_LEVEL_ID1
Text2 {
Text3, SUB_LEVEL_1_ID3
Text4, SUB_LEVEL_1_ID4
Text5 {
}
.
.
.
}
Text10, TOP_LEVEL_ID10 {
}
*IconBitmapFile, IconOrBitmapName, TOP_LEVEL_ID11
[HexValue1, . . ., HexValue16], TOP_LEVEL_ID12
[[ NumRows, NumCols, BitmapData, ...]], TOP_LEVEL_ID13
.
.
.
}
MENU and TOOLBOX are synonymous. MENUs may have up to three levels of
nesting (the top-level being the first level). Each successive level is enclosed in
braces. Like dialog boxes, IDs are assigned sequential values (starting from one)
by default. The names are stored in a header file (same base-name as the
resource file with an extension of .h). The default numbers may be changed by
following a name with an equals sign and then a number specifying the modified
ID value.
TI-89 / TI-92 Plus Developer Guide
Text6, SUB_LEVEL_2_ID6
Text7 {
Text8, SUB_LEVEL_3_ID8
Text9, SUB_LEVEL_3_ID9
}
Not for Distribution
Chapter 11: Creating the User Interface
Beta Version January 26, 2001