Chapter 11: Creating the User Interface
115
TI
-
89 / TI
-
92 Plus Developer Guide
Not for Distribution
Beta Version January 26, 2001
DlgId
can also have other special values. If it is DB_GET_TITLE, then
dValue
will
be zero and the call-back must return the text for the header of the dialog box.
This is only used if the static dialog box used the DYNHEADER field. If
DlgId
is
DB_GET_EDIT_HANDLE then
dValue
will be the field index of an HEDIT field.
See section
11.4.2.5. HEDIT
for more details.
11.5. Resource Compiler
The resource compiler (rc2.exe) is used to create dialog boxes, menus, and
pop-ups. Normally, the TI
FLASH
Studio™ (IDE) will call the Resource Compiler.
The resource compiler translates resource descriptions into internal structures
usable by the AMS. To call the Resource Compiler manually, the following syntax
is used.
rc2 [
L
mp ] resource-file
The optional switch
m
forces all common strings within menus to be merged
together, if possible, in order to save space. Due to the compacted nature of a
menu, some strings cannot be merged. The optional switch
p
calls the C
preprocessor (using com68.exe) on the resource file first. This allows a resource
file to contain any C preprocessor commands (such as #define, #include,
#ifdef, . . . ).
The resource compiler translates the resource file into an assembly language file
that defines the individual MENU or DIALOG box structures (POPUPs are
special cases of MENUs). The resource file is a standard text file (blanks, tabs,
and new-lines are skipped). A semicolon in the first column of a line denotes a
comment. Each structure is denoted by a keyword: DIALOG, TOOLBOX or
POPUP. The keyword is followed by additional fields as defined below.
Text fields in dialog boxes and menus are specified as either strings of text
delimited by double quotation marks or resource string numbers. If resource
string numbers are used, the app is responsible for supplying the text definitions
in its application frame.
Menus and pop-ups can also have ICONs or BITMAPs in place of text strings.
Icons and bitmaps can be defined in-line or in an icon/bitmap file. Icons are
defined in-line with a single left bracket followed by 16 unsigned short values
(0 . . . 0xFFFF) and a terminating right bracket. The hex values use the C syntax
of numbers so 0xABCD is the same as the decimal number 43981. Bitmaps are
defined in-line with double left brackets followed by the number of rows in the
bitmap, the number of columns, the data as a sequence of hex bytes
(0 . . . 0xFF), and finally double right brackets.
Icons and bitmaps can also be defined in an icon/bitmap file and referenced
indirectly in the resource file. The icon/bitmap file is a standard text file with the
icons and bitmaps defined as specified in the preceding paragraph. Each icon or
To Next Page
Loading...
Need help?
General
