Go to Glossary Search VisualAge C++ Help Go to VisualAge C++ Help Home Page Go to WWW VisualAge C++ Site

Generation Options

Use the Generation Options tab in the Class Editor notebook to modify the following:

Code Generation

Use the fields in Code generation group to specify the C++ header (.hpp) file. If you want to change the name that all generated and user files are based on, change the file name in the C++ header file field. The name in the Base name for other files field changes and VisualAge bases the file names for all files included in generation on this name. VisualAge writes the generated files to the current working directory.

Do not modify the contents of a generated file, because it is overwritten each time you generate part code.

When you select Generate code (.hpp and .cpp), you enable the following:

Use the User files included in generation group check boxes to select the files you want to include when VisualAge generates code for this part. These files can contain generated feature code or code that you wrote for your part.


Use this checkbox... To enable/disable inclusion of the... Included... Typical file contains...
C++ header file (.hpv)

Header file (.hpv)

Within the class part in C++ header file (.hpp) Signatures for private member functions used within the part
C++ code file (.cpv)

Code file (.cpv)

In the generated C++ code file (.cpp) Code for private member functions used within the part
Declarations file (.hv)

Resource header file (.hv)

In the generated resource header file (.h)

Resource IDs for your application
Resource file (.rcv)

Resource file (.rcv)

In the generated resource file (.rc) Text strings used in your application

.LIB File Name

Use the .LIB file name field to specify the library file (.lib) to include when you generate the source code for your part. The library file points to a DLL that contains information about a separately compiled part in your application. The .lib file name that you enter becomes the new default library file.

When you generate code for this part, VisualAge inserts a #pragma library statement for this file in the .hpp file.

Resource Generation

Use the Resource generation group to specify the following:

Generate resource IDs for strings--Use this check box to instruct VisualAge to perform the stated action. Resource generation requires both resource ID and resource .DLL.

Checking the Generate resource IDs for strings check box enables the Starting resource ID field. This field specifies a numeric resource identifier that VisualAge uses as a starting point for generating resource IDs for the part. Enable this if you expect to have your application's user interface translated into other languages.

Resource DLL name--Use this field to specify a name for the resource .DLL. This file contains the run-time strings for your part and is generated when you compile. Make sure you define this target file in your IDE configuration.

Composition Editor interface DLL name--Use this field to specify the name of the interface .DLL for your custom visual part. Your part requires this file in order to be recognized by VisualAge. The following table describes the check box options associated with this field.



Check box selected Check box not selected
.DLL Specified Full behavioral support provided for your specified .DLL. Gray box displayed.
.DLL Not Specified Gray box display. Can add to box but additions do not display. VisualAge determines what to display. You cannot add to the display.


Related concepts
Generated Interface Code
Visual, Nonvisual, and Composite Parts
Resource Files Generated for Translation
Generated Code

Related procedures
Preparing for Code Generation
Generating Source Code
Generating Resource Code for Translation
Generating User Interface Source
Defining Part Interfaces for Visual Composition
Save and Generate
Generating Feature Code
Generating Code

Related references
Save and Generate
Incorporating User-Written Code into Visual Composites
Code Generation Errors
General
User Code