Composite Control Development
Developing a composite control component can be straightforward or quite complicated. It is really up to the developer to decide how their control is going to interact with the user interface "real estate" (forms / controls) and other parts of the
application. The default templates provided with the object model provide basic interface members and memory management routines (see the
Object Model Map
for more details).
The only real limitations placed on composite control development is that each composite control must carry one unique control reference, and that the cControl object model extends only one child deep (cControlChild classes do not have children of their own).
A cControl class, however, may have multiple cControlChild classes.