48
Chapter 7: Flash Application Layout
TI
-
89 / TI
-
92 Plus Developer Guide
Not for Distribution
Beta Version January 26, 2001
range = high - low + 1;
return low + seed % range;
}
C header file pipes.h:
#ifndef _PIPES_H
#define _PIPES_H
#define P_Tools OO_FIRST_APP_STRING
➋
#define P_Clear OO_FIRST_APP_STRING+1
#endif
Resource file pipesr.r:
#include "tiams.h"
#include "pipes.h"
TOOLBOX pipesMenu, RC_NO_IDS, 0, 160 {
P_Tools {
➋
P_Clear, CM_CLEAR_ALL
}
}
➊
Pipesr.h is generated by the resource compiler.
➋
The numbering of menu commands and application strings needs some explanation. The
menu system requires all string numbers that it references to be in the range 0x000 – 0xFFF.
However, system string attributes begin at 0x800 and application string attributes begin at
0x1000. Consequently, when an app menu refers to string number 0x801, it fetches app
attribute 0x1001. The example code shows how to use macros
OO_FIRST_APP_STRING
in
the header file and
OO_FIRST_STRING
in the object frame to define menu string numbers
and their corresponding text in the app frame.
7.3.2. TI
-
BASIC Extensions
Applications can extend TI
-
BASIC with functions and programs written in C or
assembly language. The TI
-
BASIC interpreter interfaces with apps through the
OO_APP_EXT_COUNT
,
OO_APP_EXTENSIONS
, and
OO_APP_EXT_ENTRIES
attributes.
This example illustrates a simple application which implements a couple of
TI
-
BASIC extensions. The app has no user interface, hence, no event handler
entry point.
#include "tiams.h"
/* String numbers */
#define H_folders 0
#define H_vars 1
#define H_HELP 100
To Next Page
Loading...
Need help?
General
