Local and World Space - Revision history

DavidA at 07:59, 2 July 2019

2019-07-02T07:59:36Z

2014-03-07T16:42:27Z

2013-10-31T15:08:12Z

2013-10-31T15:07:57Z

2013-10-31T15:07:43Z

2013-10-31T15:06:06Z

2013-08-29T12:11:08Z

2013-08-29T11:56:54Z

2013-08-28T08:27:06Z

2013-07-29T13:57:55Z

← Older revision		Revision as of 07:59, 2 July 2019
Line 1:		Line 1:
−	~~<sidebar>Sidebar: Flowcode Help Overview:Panels</sidebar>~~
	This article discusses the difference between the position of an object on the Flowcode panel and how that position appears on screen.		This article discusses the difference between the position of an object on the Flowcode panel and how that position appears on screen.
	__NOTOC__		__NOTOC__

@@ Line 1: / Line 1: @@
-<sidebar>Sidebar: Concepts</sidebar>
+<sidebar>Sidebar: Flowcode Help Overview:Panels</sidebar>
 This article discusses the difference between the position of an object on the Flowcode panel and how that position appears on screen.
 __NOTOC__

@@ Line 18: / Line 18: @@
 ===Bounding box===
-[[File:Eg Scale Tree.svg|880px|Scaling hierarchy]]
+[[File:Eg Scale Tree.svg|400px|Scaling hierarchy]]
 The bounding box of the object is exactly the same as its position, except that instead of a ''scale'' a '''size''' is used instead. This is the scale of the object multiplied by the size of all the child objects.

@@ Line 19: / Line 19: @@
 ===Bounding box===
 [[File:Eg Scale Tree.svg|880px|Scaling hierarchy]]
 The bounding box of the object is exactly the same as its position, except that instead of a ''scale'' a '''size''' is used instead. This is the scale of the object multiplied by the size of all the child objects.

@@ Line 18: / Line 18: @@
 ===Bounding box===
-[[File:Eg Scale Tree.svg|Scaling hierarchy]]
+[[File:Eg Scale Tree.svg|880px|Scaling hierarchy]]
 The bounding box of the object is exactly the same as its position, except that instead of a ''scale'' a '''size''' is used instead. This is the scale of the object multiplied by the size of all the child objects.

← Older revision		Revision as of 12:11, 29 August 2013
Line 29:		Line 29:
	When designing and positioning objects using the graphical editor it is often easier to consider a components position in terms of '''world space''', that is the position of the object when all the objects parents are considered.		When designing and positioning objects using the graphical editor it is often easier to consider a components position in terms of '''world space''', that is the position of the object when all the objects parents are considered.

−	Flowcode will allow the world position to be controlled through the ~~properties pane~~ as this is considered the most intuitive way of picturing the system. However, local position or bounds may be selected individually for coordinates, size and rotation.	+	Flowcode will allow the world position to be controlled through the [[Properties Panel]] as this is considered the most intuitive way of picturing the system. However, local position or bounds may be selected individually for coordinates, size and rotation.

← Older revision		Revision as of 08:27, 28 August 2013
Line 1:		Line 1:
		+	<sidebar>Sidebar: Concepts</sidebar>
	This article discusses the difference between the position of an object on the Flowcode panel and how that position appears on screen.		This article discusses the difference between the position of an object on the Flowcode panel and how that position appears on screen.

@@ Line 8: / Line 8: @@
 * An ''axis'' represented by the angles ''pitch'', ''yaw'', ''roll''. These are called ''Euler angles''.
-* A [[Object Scale|scale]] to multiply the size of all [[Component tree|child objects]] by.
+* A [[Object Scale|scale]] to multiply the size of all [[Component Tree|child objects]] by.
 This defines the '''local''' position of an object. That is, the position of the object without consideration of ''any other object on the panel''.
@@ Line 20: / Line 20: @@
 The bounding box of the object is exactly the same as its position, except that instead of a ''scale'' a '''size''' is used instead. This is the scale of the object multiplied by the size of all the child objects.
-The size of a [[Component tree|leaf object]] is equal to its scale, as the object has no children to multiply its scale by. Hence the bounding box of a leaf object is the same as its local position.
+The size of a [[Component Tree|leaf object]] is equal to its scale, as the object has no children to multiply its scale by. Hence the bounding box of a leaf object is the same as its local position.