summaryrefslogtreecommitdiffstats
path: root/doc/classes/Spatial.xml
diff options
context:
space:
mode:
authorRémi Verschelde <rverschelde@gmail.com>2018-06-15 08:54:06 +0200
committerRémi Verschelde <rverschelde@gmail.com>2018-06-15 08:54:06 +0200
commit7927eb60137c49ab6eb6d591accf6409500dbc1e (patch)
treec17fa33d1f66eb462fe2c4e6e37786bef1d53d7b /doc/classes/Spatial.xml
parent8e73629def2132a057c6b444d1b867a5afd66b33 (diff)
downloadredot-engine-7927eb60137c49ab6eb6d591accf6409500dbc1e.tar.gz
doc: Remove extraneous empty lines in descriptions
Diffstat (limited to 'doc/classes/Spatial.xml')
-rw-r--r--doc/classes/Spatial.xml2
1 files changed, 0 insertions, 2 deletions
diff --git a/doc/classes/Spatial.xml b/doc/classes/Spatial.xml
index 46f2bedfc2..d9242d8c42 100644
--- a/doc/classes/Spatial.xml
+++ b/doc/classes/Spatial.xml
@@ -5,7 +5,6 @@
</brief_description>
<description>
Most basic 3D game object, with a 3D [Transform] and visibility settings. All other 3D game objects inherit from Spatial. Use Spatial as a parent node to move, scale, rotate and show/hide children in a 3D project.
-
Affine operations (rotate, scale, translate) happen in parent's local coordinate system, unless the Spatial object is set as top level. Affine operations in this coordinate system correspond to direct affine operations on the Spatial's transform. The word local below refers to this coordinate system. The coordinate system that is attached to the Spatial object itself is referred to as object-local coordinate system.
</description>
<tutorials>
@@ -284,7 +283,6 @@
</member>
<member name="rotation" type="Vector3" setter="set_rotation" getter="get_rotation">
Rotation part of the local transformation, specified in terms of YXZ-Euler angles in the format (X-angle, Y-angle, Z-angle), in radians.
-
Note that in the mathematical sense, rotation is a matrix and not a vector. The three Euler angles, which are the three indepdent parameters of the Euler-angle parametrization of the rotation matrix, are stored in a [Vector3] data structure not because the rotation is a vector, but only because [Vector3] exists as a convenient data-structure to store 3 floating point numbers. Therefore, applying affine operations on the rotation "vector" is not meaningful.
</member>
<member name="rotation_degrees" type="Vector3" setter="set_rotation_degrees" getter="get_rotation_degrees">