|
|
@@ -1,6 +1,6 @@
|
|
|
= The SceneExplorer
|
|
|
-:author:
|
|
|
-:revnumber:
|
|
|
+:author:
|
|
|
+:revnumber:
|
|
|
:revdate: 2016/03/17 20:48
|
|
|
:relfileprefix: ../../
|
|
|
:imagesdir: ../..
|
|
|
@@ -12,7 +12,7 @@ ifdef::env-github,env-browser[:outfilesuffix: .adoc]
|
|
|
|
|
|
If your plugin brings in its own SceneGraph objects you can still have them work like any other SceneExplorer item, including its special properties.
|
|
|
|
|
|
-If you want to support special properties of your objects that are not exposed by the SDK automatically, you will have to create your own class that extends org.openide.nodes.Node and implement the interface com.jme3.gde.core.sceneexplorer.nodes.AbstractSceneExplorerNode. Then you register that class by adding
|
|
|
+If you want to support special properties of your objects that are not exposed by the SDK automatically, you will have to create your own class that extends org.openide.nodes.Node and implement the interface com.jme3.gde.core.sceneexplorer.nodes.AbstractSceneExplorerNode. Then you register that class by adding
|
|
|
|
|
|
[source]
|
|
|
----
|
|
|
@@ -178,7 +178,7 @@ public class JmeGhostControl extends AbstractSceneExplorerNode {
|
|
|
|
|
|
set.put(makeProperty(obj, Vector3f.class, "getPhysicsLocation", "setPhysicsLocation", "Physics Location"));
|
|
|
set.put(makeProperty(obj, Quaternion.class, "getPhysicsRotation", "setPhysicsRotation", "Physics Rotation"));
|
|
|
-
|
|
|
+
|
|
|
set.put(makeProperty(obj, CollisionShape.class, "getCollisionShape", "setCollisionShape", "Collision Shape"));
|
|
|
set.put(makeProperty(obj, int.class, "getCollisionGroup", "setCollisionGroup", "Collision Group"));
|
|
|
set.put(makeProperty(obj, int.class, "getCollideWithGroups", "setCollideWithGroups", "Collide With Groups"));
|
|
|
@@ -304,7 +304,7 @@ public class NewRigidBodyAction extends AbstractNewControlAction {
|
|
|
----
|
|
|
|
|
|
|
|
|
-==== Adding using a Wizard
|
|
|
+=== Adding using a Wizard
|
|
|
|
|
|
You can create a new wizard using the wizard template in the SDK (New File→Module Development→Wizard). The Action that the template creates can easily be changed to one for adding a Control or Spatial or for applying a Tool. Note that we extend AbstractNewSpatial*Wizard*Action here.
|
|
|
|
|
|
@@ -407,4 +407,3 @@ public class AddSkyboxAction extends AbstractNewSpatialWizardAction {
|
|
|
====
|
|
|
The abstract spatial and control actions implement undo/redo automatically, for the ToolActions you have to implement it yourself.
|
|
|
====
|
|
|
-
|
mitm