- All Implemented Interfaces:
public class SoPointLightManip extends SoPointLightPoint light node with 3D interface for editing location.
SoPointLightManipis the base class for all
SoPointLightnodes that have a built-in 3D user interface (this is the only such class provided with the Open Inventor toolkit). Since it is derived from
SoPointLight, any changes to its fields result in a change of lighting for nodes that follow it in the scene graph. In this case, the interface edits the location field. Also, the color of the manipulator's geometry will reflect the color of the light (but you can not edit the color using this manipulator).
Typically, you will want to replace a regular
SoPointLightManip(as when the user selects a light to be edited), or vice versa (as when the user is done moving the light and the interface should go away). Use the
replaceNode()method to insert a manipulator into a scene graph, and the
replaceManip()method to remove it when done.
SoPointLightDraggerto provide a 3D interface. However, the manipulator differs from the dragger; it lights other objects in the scene because, as an
SoPointLight, it alters the state. The fields values and movement of the dragger, on the other hand, affect only the dragger itself. To find out more about how the interface works and what each part will do, see the reference page for
SoPointLightDragger. The interfaces of the dragger and the manipulator are identical.
SoPointLightManiputilizes its dragger by adding it as a hidden child. When an action is applied to the manipulator, such as rendering or handling events, the manipulator first traverses the dragger, and then the manipulator adds its lighting parameters to the state. When you click-drag-release over the manipulator, it passes these events down to the dragger, which moves as a result ("I can't <B> help </B> it, I'm a dragger!").
The manipulator maintains consistency between the fields of the dragger and its own fields. Let's say you use the mouse to translate the dragger . Callbacks insure that the location field of the manipulator will change by the same amount, thus changing the lighting of nodes which follow in the scene graph. Similarly, if you set the location field of the
SoPointLightManip, the manipulator will place the dragger accordingly.
Because the dragger is a hidden child, you can see the dragger on screen and interact with it, but the dragger does not show up when you write the manipulator to file. Also, any
SoPathwill end at the manipulator. (See the Actions section of this reference page for a complete description of when the dragger is traversed).
You can get this dragger from the manipulator using the
getDragger()method. You will need to do this if you want to change the geometry of a manipulator, since the geometry actually belongs to the dragger.
on true intensity 1 color 1 1 1 location 0 0 1
First, traverses the dragger the way an
SoGroupwould. All draggers place themselves in space, but leave the current transformation unchanged when finished. Then the
SoPointLightManipadds a point light into the state, just like its base class,
Searches just like an
SoPointLight. Does not search the dragger, which is a hidden child.
Writes out just like an
SoPointLight. Does not write the dragger, which is a hidden child. If you really need to write valuable information about the dragger, such as customized geometry, you can retrieve the dragger with the
getDragger()method and then write it out separately.
Nested Class Summary
Nested classes/interfaces inherited from class com.openinventor.inventor.nodes.SoNode
Nested classes/interfaces inherited from class com.openinventor.inventor.Inventor
Fields inherited from class com.openinventor.inventor.nodes.SoPointLight
Fields inherited from class com.openinventor.inventor.Inventor
Constructors Constructor Description
All Methods Instance Methods Concrete Methods Modifier and Type Method Description
getDragger()Returns the dragger being used by this manipulator.
replaceManip(SoPath p, SoPointLight newOne)Replaces the tail of the path, which must be this manipulator, with the given
replaceNode(SoPath p)Replaces the tail of the path with this manipulator.
Methods inherited from class com.openinventor.inventor.nodes.SoNode
affectsState, callback, copy, copy, distribute, doAction, getAlternateRep, getBoundingBox, getByName, getMatrix, getPrimitiveCount, getRenderEngineMode, getRenderUnitID, GLRender, GLRenderBelowPath, GLRenderInPath, GLRenderOffPath, grabEventsCleanup, grabEventsSetup, handleEvent, isBoundingBoxIgnoring, isOverride, pick, rayPick, search, setOverride, touch, write
Methods inherited from class com.openinventor.inventor.fields.SoFieldContainer
copyFieldValues, copyFieldValues, enableNotify, fieldsAreEqual, get, getAllFields, getEventIn, getEventOut, getField, getFieldName, hasDefaultValues, isNotifyEnabled, set, setToDefaults
Methods inherited from class com.openinventor.inventor.misc.SoBase
dispose, getName, isDisposable, isSynchronizable, setName, setSynchronizable
Methods inherited from class com.openinventor.inventor.Inventor
public boolean replaceManip(SoPath p, SoPointLight newOne)Replaces the tail of the path, which must be this manipulator, with the given
SoPointLightnode. If the path has a nodekit, this will try to use setPart() to insert the new node. Otherwise, the manipulator requires that the next to last node in the path chain be a group.
The field values from the manipulator will be copied to the point light node, and the manipulator will be replaced.
The manipulator will not make any changes to field connections. The calling process is thus responsible for keeping track of its own nodes and field connections.
public boolean replaceNode(SoPath p)Replaces the tail of the path with this manipulator. The tail of the path must be an
SoPointLightnode (or subclass thereof). If the path has a nodekit, this will try to use setPart() to insert the manipulator. Otherwise, the manipulator requires that the next to last node in the path chain be a group.
The field values from the point light node will be copied to this manipulator, and the light node will be replaced.
The old node will disappear if it has no references other than from the input path p and its parent, since this manipulator will be replacing it in both of those places. Nor will the manipulator make any changes to field connections of the old node. The calling process is thus responsible for keeping track of its own nodes and field connections.