Global and static local variables are stored in a fixed block called
dgroup. This remains in memory for the duration of your application.
> 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
> are displayed. When the program is run, it has to do some initialising,
> and I want to tell the user that this is happening. So that the user can
> see these messages, I have to wait until the window is ready before
> starting. If I don't, initialisation is complete by the time the window is
> drawn. Currently, the first time my window's MSG_META_REDRAW is called, it
> sends a message back to the process to tell it to start initialising. Not
> only is this very nasty, it only works on the EC version. The NC version
> doesn't display anything at all.
Try MSG_VIS_OPEN.
> 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.
Make a local.mk file like this:
CCOM_FLAGS += -P
#include <$(SYSMAKEFILE)>
If that doesn't work, then change the compiler.mk file in the Include
directory.
Nathan