GEOS SDK TechDocs
|
| 
| 
1 VisContent Instance Data
| 
2.1 Setting Up Sizing Behavior
You will probably not have to subclass
VisContentClass
unless you are using a large document or you want the content to draw something in response to a
MSG_VIS_DRAW
. In most other cases, you can declare your content object directly on
VisContentClass
.
Most VisContent behavior is inherited directly from
VisCompClass
. Some additional behavior is detailed in the following sections.
If you are planning on using the document control objects with GenViews, you will not need VisContent objects. The GenDocument resolves at run-time into a subclass of VisContent and therefore replaces the need for an explicitly-defined VisContent object. See the Documents chapter for full information on GenDocuments.
Messages Received from the View
GEOS SDK TechDocs
|
|
| 1 VisContent Instance Data
| 2.1 Setting Up Sizing Behavior