Before generating code, you must set generation options in the
Class Editor. A summary of tasks associated with these settings
follows.
-
- Enabling code generation
- To enable generation of class code, select the Generate
code (.hpp and .cpp) check box.
To enable
generation of feature code, select the appropriate check
boxes in the User files included in generation
group. This selection also ensures that feature files are
properly included in the generated class files.
- Specifying a name for generated files
- By default, VisualAge sets a name for generated files.
However, you can change the default by modifying the
contents of the C++ header file field. When this
value is changed, the value of the Base name for other
files field is also changed.
- Including handwritten code files
- Before VisualAge can generate the proper include
statements for handwritten code, you must select the
appropriate check boxes in the User files included in
generation group.
- Linking in a part that will be compiled separately
- If the part will be compiled separately into a runtime
DLL, you can indicate so to VisualAge by entering the
name of the link library file in the .LIB file name
field. If this is set, VisualAge generates a #pragma
library statement in the.hpp file for the part.
- Using a resource DLL
- If the part uses resources in a separate DLL, you must
indicate so to VisualAge by entering a value in the Resource
DLL name field.
- Enabling custom visual support
- To enable behavioral support for a custom visual part on
the free-form surface, enter the name of the part's
interface DLL in the Composition Editor interface DLL
name field and select the Use interface DLL
check box.
Selecting the check box indicates to
VisualAge that you want the part instantiated
"live" on the free-form surface. If you do not
select the check box, VisualAge uses a gray box to
represent the part on the free-form surface.
Generated Code
Generating Source Code
Generating Resource Code for
Translation
Generating User Interface
Source
Class Editor