RSCTOC is a resource file 'disassembler', that is it takes the output of
a resource construction set and converts it into C source code. The point
of this is that it can be more convenient to have the program in one piece,
especially when it may be launched from another directory, which tends to
cause problems when a '.RSC' file is used.

The dialog boxes in the GEMmed version of the program should be self
explanatory - the name of the source and destination files can be typed
directly into the dialog or chosen from file selectors which appear when
the editable boxes are clicked on.

The original RSCTOC allows a unique prefix to be applied to the variable
names and the 'fix' procedure and this is the third editable box.

The use of the output from RSCTOC can be seen in the listing of the program
itself - the resource used in the program was created using the program!
I would recommend that you keep the resource source file separate from the
main program to allow further changes to be made without causing extra work.

In use the first step is to call fix_objects() to make the trees usable at
this stage. Next get the address of the object trees, of course it is no
longer necessary to call rsrc_load. These addresses are held in the
rs_trindex array in the code produced by RSCTOC. Declare this in the main
body of the program as:

				extern OBJECT *rs_trindex[];

It is necessary to #include the '.h' file produced by the RCP in order to
be able to use the object names in the program.

The usual OBJECT pointers can then be used:

				OBJECT *dialog_box;
				.
				.
				.
				dialog_box = rs_trindex[0];

and assignment used instead of calling rsrc_gaddr. After this the resources
can be used normally.

I have included the resource files used in RSCTOC, these are not, of
course, necessary to run the program.