The Instance Network
Introduction
The widgets and objects in the EditTable Widget Library can only be created
as children of certain specific classes of widgets. Conversely, a widget
accepts only certain types of widgets and/or objects as children. The following
paragraphs describe the parent/child restrictions for INT widgets and objects.
CompBase Class
You cannot create an instance of this widget class because it serves only as
a base (metaclass) for the INT composite widgets.
EditObject Widget
You cannot create an instance of this widget class because it serves only as
a base (metaclass) for the INT composite widgets.
EditTable Widget
An EditTable widget can be a child of any widget that accepts an XmManager
widget as a child (such as XmForm or TopLevelShell). Often, an EditTable widget
will be the child of an instance of the XintScroll widget class. Since
EditTable is a subclass of XintEditObject, an EditTable widget can have
children that are Graphic objects.
Scroll Widget
An XintScroll instance can be a child of any widget that accepts XmManager as
a child (such as XmForm or TopLevelShell). XintScroll can control the scrolling
of only one EditTable widget.
Graphic Objects
Objects are always managed automatically by their widget parent. Because of
this special relationship between objects and their parents, there are
stringent restrictions on who can be a parent of a specific type of object.
Note also that INT Graphic objects cannot have children. INT Graphic objects
must be children of an EditTable widget.