Merged changes in the trunk up to revision 43881.
This commit is contained in:
@@ -69,11 +69,9 @@ See the actuator's reference for available methods
|
||||
:columns: 3
|
||||
|
||||
* :class:`~bge.types.BL_ActionActuator`
|
||||
* :class:`~bge.types.BL_ShapeActionActuator`
|
||||
* :class:`~bge.types.KX_CameraActuator`
|
||||
* :class:`~bge.types.KX_ConstraintActuator`
|
||||
* :class:`~bge.types.KX_GameActuator`
|
||||
* :class:`~bge.types.KX_IpoActuator`
|
||||
* :class:`~bge.types.KX_NetworkMessageActuator`
|
||||
* :class:`~bge.types.KX_ObjectActuator`
|
||||
* :class:`~bge.types.KX_ParentActuator`
|
||||
@@ -477,6 +475,7 @@ Action Actuator
|
||||
See :class:`bge.types.BL_ActionActuator`
|
||||
|
||||
.. data:: KX_ACTIONACT_PLAY
|
||||
.. data:: KX_ACTIONACT_PINGPONG
|
||||
.. data:: KX_ACTIONACT_FLIPPER
|
||||
.. data:: KX_ACTIONACT_LOOPSTOP
|
||||
.. data:: KX_ACTIONACT_LOOPEND
|
||||
@@ -635,21 +634,6 @@ See :class:`bge.types.KX_GameActuator`
|
||||
.. data:: KX_GAME_SAVECFG
|
||||
.. data:: KX_GAME_LOADCFG
|
||||
|
||||
.. _ipo-actuator:
|
||||
|
||||
------------
|
||||
IPO Actuator
|
||||
------------
|
||||
|
||||
See :class:`bge.types.KX_IpoActuator`
|
||||
|
||||
.. data:: KX_IPOACT_PLAY
|
||||
.. data:: KX_IPOACT_PINGPONG
|
||||
.. data:: KX_IPOACT_FLIPPER
|
||||
.. data:: KX_IPOACT_LOOPSTOP
|
||||
.. data:: KX_IPOACT_LOOPEND
|
||||
.. data:: KX_IPOACT_FROM_PROP
|
||||
|
||||
---------------
|
||||
Parent Actuator
|
||||
---------------
|
||||
@@ -691,20 +675,6 @@ See :class:`bge.types.KX_SceneActuator`
|
||||
.. data:: KX_SCENE_SUSPEND
|
||||
.. data:: KX_SCENE_RESUME
|
||||
|
||||
.. _shape-action-actuator:
|
||||
|
||||
---------------------
|
||||
Shape Action Actuator
|
||||
---------------------
|
||||
|
||||
See :class:`bge.types.BL_ActionActuator`
|
||||
|
||||
.. data:: KX_ACTIONACT_PLAY
|
||||
.. data:: KX_ACTIONACT_FLIPPER
|
||||
.. data:: KX_ACTIONACT_LOOPSTOP
|
||||
.. data:: KX_ACTIONACT_LOOPEND
|
||||
.. data:: KX_ACTIONACT_PROPERTY
|
||||
|
||||
.. _logic-sound-actuator:
|
||||
|
||||
--------------
|
||||
|
||||
@@ -123,6 +123,29 @@ Example of a data path that can be quickly found via the console:
|
||||
1.0
|
||||
|
||||
|
||||
Data Creation/Removal
|
||||
^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
Those of you familiar with other python api's may be surprised that new datablocks in the bpy api can't be created by calling the class:
|
||||
|
||||
>>> bpy.types.Mesh()
|
||||
Traceback (most recent call last):
|
||||
File "<blender_console>", line 1, in <module>
|
||||
TypeError: bpy_struct.__new__(type): expected a single argument
|
||||
|
||||
|
||||
This is an intentional part of the API design.
|
||||
The blender/python api can't create blender data that exists outside the main blender database (accessed through bpy.data), because this data is managed by blender (save/load/undo/append... etc).
|
||||
|
||||
Data is added and removed via methods on the collections in bpy.data, eg:
|
||||
|
||||
>>> mesh = bpy.data.meshes.new(name="MyMesh")
|
||||
>>> print(mesh)
|
||||
<bpy_struct, Mesh("MyMesh.001")>
|
||||
|
||||
>>> bpy.data.meshes.remove(mesh)
|
||||
|
||||
|
||||
Custom Properties
|
||||
^^^^^^^^^^^^^^^^^
|
||||
|
||||
|
||||
Reference in New Issue
Block a user