public class SoBaseKit extends SoNode implements SoGetView
SoShapeKit
).
Each class of nodekit has a nodekit catalog (SoNodekitCatalog
) that describes the nodes in the subgraph, referred to as parts . The catalog has an entry for each part, with information such as the partName , partType , and nullByDefault (if false the constructor creates it). The catalog also describes the arrangement of parts in the subgraph. (Other information is described below; a complete description is in the SoNodekitCatalog
reference page.)
If we regard the scene graph arrangement as a branching tree, then the top node (root) of the arrangement is always the nodekit itself. The leaf nodes are those at the bottom (containing no children). Some leaves of the tree are defined in the catalog to be public parts, while other leaves are private . All non-leaf parts are considered internal to the nodekit structure and are marked private. Public parts are accessible; they may be requested, changed, or set by the programmer with member functions such as getPart()
. Private parts are not accessible, so methods such as getPart()
will have no effect on them. For example, if you call getPart()
to retrieve a private part, NULL will be returned even when the part exists.
Every nodekit reference page has a Parts section describing the function of each public part it adds to those inherited from its parent class. Also, a Catalog Parts section has tables of often-needed information from the catalog (part type, etc.). These tables include all public parts, both new and inherited. Only the public parts of a nodekit are described in the reference pages. Nodekits take care of the rest for you; they automatically arrange the subgraph, creating and deleting the private parts when necessary. (The SoNodekitCatalog
reference page has methods for finding out the part names and arrangement of all parts, both public and private.)
The nodekit catalog is a template shared by all instances of a class. They use the shared catalog as a guide when creating parts (i.e., constructing actual nodes), but each instance stores its own parts separately. Moreover, nodekits are not SoGroup
nodes, and parts are added as hidden children ; you can only access parts with the methods of SoBaseKit
and its derived classes.
Any public part may be retrieved with getPart()
, installed with setPart()
, or removed by giving a NULL argument to setPart()
. Paths from the nodekit down to a part can be created by createPathToPart().
By default, parts are not created until the user requests or sets them. This keeps the subgraph uncluttered and efficient for traversal. Additionally, removing a part (setting it to NULL) has the extra effect of removing any internal parts that are no longer needed.
Since nodekits hide their children, any SoPath
containing nodekits will end at the topmost nodekit. However, since nodekits may be nested within other nodekits, you may wish to cast an (SoPath
*) into an (SoNodeKitPath *). The methods of SoNodeKitPath allow you to view all nodekits that lie on the path (see the reference page for SoNodeKitPath).
Public parts in the nodekit catalog fall into three categories:
getPart()
below shows how to refer to nested parts by name (e.g., "appearance.material"). This works for any nodekit method that takes a part name for an argument.
getPart()
(e.g., "childList[0]", or if the list elements are in turn nodekits, "childList[2].transform").
When the catalog denotes that a part is a list, the part itself is always a node of type SoNodeKitListPart
. The catalog specifies a set of permissible listItemTypes and a listContainerType for that part. It gives this information to the SoNodeKitListPart
when it creates it. From then on, the list part will enforce type checking. So even if you retrieve the SoNodeKitListPart
with getPart()
, you will not be able to add illegal children. (See the SoNodeKitListPart
reference page for more information). As an example, the callbackList part of SoBaseKit
has an SoSeparator
container and allows only SoCallback
and SoEventCallback
nodes in the list. Children may be added, retrieved, and removed from an SoNodeKitListPart
node using methods that parallel those of SoGroup
. However, type-checking is strictly enforced.
Note that, although all public parts are leaves in the nodekit catalog, you are free to add children to them (assuming that they are groups, nodekits, or list parts). A part's status as a leaf in the catalog just means that the nodekit will not manage the part's children. For example, SoWrapperKit
has a part called contents with a part type of SoSeparator
. You can put whatever you want underneath the separator, as long as contents itself is an SoSeparator
.
Thus, a nodekit only controls a section of the scene graph. Above and below that section, anything goes.
However, when nodekits are nested, they effectively create a larger `known' section of the scene graph. For example, the appearance part of the SoSeparatorKit
is a leaf node in the SoSeparatorKit
catalog. But appearance is in turn an SoAppearanceKit
, containing parts such as material and drawStyle. The two nodekits combine to make an even larger template, which the SoSeparatorKit
can examine by looking at the catalogs for both classes. So an SoSeparatorKit
can successfully return a part named "material"; first it finds (or creates) the appearance part, then it gets the material by calling getPart()
on the appearance .
When the catalog defines the listItemTypes of a list part to be nodekits, the name-able space expands further. For example, SoSeparatorKit
has a part childList which permits only SoSeparatorKits, so each list element can be further searched. Hence the name "childList[0].childList[1].childList[2].material" is perfectly legal.
(SoNodeKitListPart
) callbackList
This is the only part that the base class SoBaseKit
creates. It is a public part that is inherited by all nodekits. It provides an easy way to add callbacks for a nodekit to use during action traversal (e.g. SoHandleEventAction
). It is a list part and may contain numerous SoCallback
and/or SoEventCallback
nodes.
File format/default:
BaseKit {
callbackList | NULL |
boundingBoxIgnoring | false |
Action behavior:
SoGLRenderAction
, SoCallbackAction
, SoGetBoundingBoxAction
, SoHandleEventAction
Behaves like an SoGroup
. Traverses each child in order.
SoRayPickAction
Traverses each child in order. Then, for any pick containing the kit on its path, makes an SoNodeKitDetail
as follows: Sets the "detailNodeKit" (retrievable with SoNodeKitDetail.getNodeKit()
) to refer itself. Sets the "detailPart" (retrievable with SoNodeKitDetail.getPart()
) to refer the kit's leaf-most part that lies on the pickPath. Sets the "detailPartName" (retrievable with SoNodeKitDetail.getPartName()
) to be the partName of that part, as found in the catalog.
Does not descend into nested nodekits. Each nodekit along the path is the "detailPart" in its parent's detail. However, if the pick path goes through a list part, the child is used for the "detailPart", and "detailPartName" is of the form "listName[i]".
SoGetMatrixAction
Behaves like an SoGroup
. Does nothing unless the kit is in the middle of the path chain the action is being applied to. If so, the children up to and including the next node in the chain are traversed.
SoSearchAction
First, searches itself like an SoNode
. Then, checks the value of isSearchingChildren()
. If true, traverses the children in order. If false, returns.
SoWriteAction
Begins by writing out regular fields, then writes out the parts. A nodekit does not write out its parts the way an SoGroup
writes out its children. Instead, it writes each part as an SoSFNode
field. First the partName is written, then the node being used for that part.
To keep the files terse, nodekits write out as few parts as possible. However, nodekits always write a part if another instance or a path is writing it. If this is not the case, parts are left out according to the following rules:
SoGroup
and SoSeparator
nodes do not write.
All Parts
Part Name | Part Type | Default Type | NULL Default |
callbackList | NodeKitListPart | yes |
Extra Information for List Parts from Above Table
Part Name | Container Type | Possible Types |
callbackList | Separator | Callback, EventCallback |
See also:
SoAppearanceKit
, SoCameraKit
, SoLightKit
, SoNodeKit, SoNodeKitDetail
, SoNodeKitListPart
, SoNodeKitPath, SoNodekitCatalog
, SoSceneKit
, SoSeparatorKit
, SoShapeKit
, SoWrapperKit
Inventor.ConstructorCommand
Modifier and Type | Field and Description |
---|---|
SoSFBool |
boundingBoxIgnoring
Whether to ignore this node during bounding box traversal.
|
VERBOSE_LEVEL, ZeroHandle
Constructor and Description |
---|
SoBaseKit()
Constructor.
|
Modifier and Type | Method and Description |
---|---|
static SoNodekitCatalog |
getClassNodekitCatalog()
Returns the
SoNodekitCatalog for the class SoBaseKit . |
SoNodekitCatalog |
getNodekitCatalog()
Returns the
SoNodekitCatalog for this instance of SoBaseKit . |
SoNode |
getPart(java.lang.String partName)
equivalent to
getPart (partName,true) |
SoNode |
getPart(java.lang.String partName,
boolean makeIfNeeded)
Searches the nodekit catalog (and those of all nested nodekits) for the part named partName.
|
java.lang.String |
getPartString(SoBase part)
Given a node or a path to a node, checks if the part exists in the nodekit, in a nested nodekit, or an element of a list part.
|
boolean |
getViewportIsEnabled()
Returns true if SoGetView functionalities are enabled, false otherwise.
|
SbVec2f |
getViewportOrigin()
Returns SbViewportRegion origin.
|
SbVec2f |
getViewportSize()
Returns SbViewportRegion size.
|
static boolean |
isSearchingChildren()
Returns true if nodekit children are searched during
SoSearchAction traversal. |
boolean |
set(java.lang.String nameValuePairListString)
This function allows field values of parts (nodes) to be set in several different parts simultaneously.
|
boolean |
set(java.lang.String partNameString,
java.lang.String parameterString)
This function allows field values of parts (nodes) to be set.
|
boolean |
setPart(java.lang.String partName,
SoNode newPart)
Inserts the given node (not a copy) as the new part specified by partName.
|
static void |
setSearchingChildren(boolean newVal)
Sets if nodekit children are searched during
SoSearchAction traversal. |
affectsState, callback, copy, copy, distribute, doAction, getAlternateRep, getBoundingBox, getByName, getMatrix, getPrimitiveCount, getRenderUnitID, GLRender, GLRenderBelowPath, GLRenderInPath, GLRenderOffPath, grabEventsCleanup, grabEventsSetup, handleEvent, isBoundingBoxIgnoring, isOverride, pick, rayPick, search, setOverride, touch, write
copyFieldValues, copyFieldValues, enableNotify, fieldsAreEqual, get, getAllFields, getEventIn, getEventOut, getField, getFieldName, hasDefaultValues, isNotifyEnabled, setToDefaults
dispose, getEXTERNPROTO, getName, getPROTO, isDisposable, isSynchronizable, setName, setSynchronizable
getAddress, getNativeResourceHandle, startInternalThreads, stopInternalThreads
public final SoSFBool boundingBoxIgnoring
public boolean getViewportIsEnabled()
getViewportIsEnabled
in interface SoGetView
public SbVec2f getViewportOrigin()
getViewportOrigin
in interface SoGetView
public SbVec2f getViewportSize()
getViewportSize
in interface SoGetView
public static boolean isSearchingChildren()
SoSearchAction
traversal.
By default, they are not.public boolean set(java.lang.String partNameString, java.lang.String parameterString)
SoSeparatorKit
has a part named material which is of type SoMaterial
.public static SoNodekitCatalog getClassNodekitCatalog()
SoNodekitCatalog
for the class SoBaseKit
.public static void setSearchingChildren(boolean newVal)
SoSearchAction
traversal.
By default, they are not.public SoNodekitCatalog getNodekitCatalog()
SoNodekitCatalog
for this instance of SoBaseKit
.
While each instance of a given class creates its own distinct set of parts (which are actual nodes), all instances share the same catalog (which describes the parts but contains no actual nodes).public boolean setPart(java.lang.String partName, SoNode newPart)
getPart()
for the syntax of partName. This method adds any extra nodes needed to fit the part into the nodekit's catalog. Run-time type checking verifies that the node type of newPart matches the type called for by partName. For example, if partName was a material for an SoSeparatorKit
, but newPart was an SoTransform
node, then the node would not be installed, and false would be returned.
If newPart is NULL, then the node specified by partName is removed. If this renders any private parts useless (as occurs when you remove the last child of an SoGroup
node), they will also be removed. Hence nodekits do not retain unnecessary nodes.
true is returned on success, and false upon error.
public boolean set(java.lang.String nameValuePairListString)
set
in class SoFieldContainer
public SoNode getPart(java.lang.String partName, boolean makeIfNeeded)
getPart()
will create the part (as well as any necessary intermediary parts), put it in the correct place, and return the newly created part.
Elements of list parts and parts within nested nodekits can all be retrieved with getPart()
The full syntax for legal partName arguments is given below.
Part name BNF notation :
partName = singleName | compoundName
compoundName = singleName | compoundName.singleName
singleName = singlePartName | singleListElementName
singlePartName = the name of any single part in the catalog (including those that are lists or nodekits), or in the recursively nested catalogs of any of its parts.
singleListElementName = singleListName[index]
singleListName = the name of any single list-type part in the catalog, or in the recursively nested catalogs of any of its parts.
index = integer
Examples of valid part names are:
"transform", "appearance.material", "childList[2].drawStyle", "foot", "bird.leftLeg.foot", "octopus.leg[4].suctionCup[2].material"
public java.lang.String getPartString(SoBase part)
Generated on January 23, 2025, Copyright © Thermo Fisher Scientific. All rights reserved. http://www.openinventor.com