Try a huge arrary.
>2. How are global and static variables stored? I presume that they're put
>in the relevant code resource. But, code resources should be discardable.
Probably stored in dgroup, which would be fixed memory. I know that's true
for assembly.
>3. Is there any message that is received when the user interface tree is
>built and ready? My program has a window in which various status messages
I think you want MSG_GEN_PROCESS_OPEN_APPLICATION. If you want the changes
to show happen before the UI is first drawn, do your work before putting the
@callsuper. Just don't forget the @callsuper. Fair warning, Geoworks doesn't
recommend this, but I have had absolutely no problems with it, and have used
it to get around some really wierd dynamic geometry problems.
>4. Is there any reason why I can't use the -P option to BCC to tell it to
>build in C++ mode? This will let me use some C++ constructs such as //
>comments and declaring variables as I need them. This would let me tidy my
>code somewhat.
Just don't try to use C++ objects, classes, or iostreams and I can't think
of anything that would cause a problem.
-------------------------------------------------------------------
| Edward Di Geronimo Jr. edwdig@bergen.org |
-------------------------------------------------------------------