The Benefits of Creating Controls in C.R.:
When you create a control in the Control
Repository, it appears in the RadVC toolbox along with other standard C++ controls (e.g.
command buttons, textbox etc.) and thus they become available to all Visual C++ projects.
This makes the control re-use very convenient since you do not need to install a control
into the RadVC toolbox each time you want to use the control in a project.
How to Create or
Install Controls in C.R.:
To create a new control in the C.R., you
need to make sure that the checkbox named "Add to Control Repository" is checked
in the "New C++ Control" dialog. Please visit "Creating
New C++ Control" page to find more on how to create a new RAD C++ control by
invoking the "New C++ Control" dialog. Also go to "Installing
New C++ Control" page to find how you can install a RAD C++ control in the C.R.
How RadVC Manages
Controls in C.R.: RadVC stores the various
files of a RAD C++ control in the following RadVC directories:
| File
Type |
File
Extension |
Storage
Location |
| Declaration |
.h, .hpp etc. |
\\RadVC\Include |
| Implementation |
.cpp, .c etc. |
\\RadVC\Src |
| Resource
Description |
.rc |
\\RadVC\Src |
| Resource
Definition |
.rh |
\\RadVC\Include |
| Resource |
.bmp. ico,
.cur etc. |
\\RadVC\Res |
| Library |
.lib |
\\RadVC\Lib |
| Dynamic Link
Library(DLL) |
.dll |
\\RadVC\Dll |
| ActiveX |
.ocx |
\\RadVC\ActiveX |
The information on the files constituting a
RAD C++ control is saved in a text file called "ToolList.txt", which can be
located in the main RadVC directory.
How RadVC Manages
Control Resources in C.R. (for "Source" type controls):
In order to avoid duplicate resource ID's,
RadVC maintains system level constants for various resource and control constants (for
"Source" type controls). Thus whenever a new RAD C++ control is installed in the
C.R., the resource ID's are modified to make sure that they remain unique throughout the
system. |
