Object Scale - Revision history

SteveT: /* Flowcodes representation of scale */

2026-07-23T14:41:32Z

Flowcodes representation of scale

← Older revision		Revision as of 14:41, 23 July 2026
Line 6:		Line 6:
	Flowcode represents an objects [[Object Position\|position]] in terms of [[Object Coordinates\|coordinates]], '''scale''' and [[Object Rotation\|rotation]].		Flowcode represents an objects [[Object Position\|position]] in terms of [[Object Coordinates\|coordinates]], '''scale''' and [[Object Rotation\|rotation]].

	Internally an objects scale is kept as a ''scale factor'' in the X, Y and Z axis of the object. When accessing the [[~~API Overview~~\|SIM API]] this is the value that is altered, and relates to the diagonal of a transform matrix:		Internally an objects scale is kept as a ''scale factor'' in the X, Y and Z axis of the object. When accessing the [[Simulation_Functionality\|SIM API]] this is the value that is altered, and relates to the diagonal of a transform matrix:

	::[[File:Eg Object Scale.png]]		::[[File:Eg Object Scale.png]]
Line 13:		Line 13:

	All API functions deal with this scale - this is mainly because the calculations involved in converting to other representations and back every time scale needs to be set would slow the programs down, but also because conversion to other representations can result in rounding errors and inaccuracies when combined with rotation.		All API functions deal with this scale - this is mainly because the calculations involved in converting to other representations and back every time scale needs to be set would slow the programs down, but also because conversion to other representations can result in rounding errors and inaccuracies when combined with rotation.


	== Scale vs Size==		== Scale vs Size==

MartinW at 14:33, 14 September 2023

2023-09-14T14:33:44Z

← Older revision		Revision as of 14:33, 14 September 2023
Line 1:		Line 1:
	This article refers to the representation of an object drawn on either the [[2d_Panels]] or the [[System_Panel]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.		This article refers to the representation of an object drawn on either the [[2d_Panels\|2D panels]] or the [[System_Panel\|3D system panel]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.

	__NOTOC__		__NOTOC__

MartinW at 14:32, 14 September 2023

2023-09-14T14:32:35Z

← Older revision		Revision as of 14:32, 14 September 2023
Line 1:		Line 1:
	This article refers to the representation of an object drawn on either the [[~~System Panel~~]] or the [[~~Dashboard Panel~~]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.		This article refers to the representation of an object drawn on either the [[2d_Panels]] or the [[System_Panel]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.

	__NOTOC__		__NOTOC__

DavidA at 07:59, 2 July 2019

2019-07-02T07:59:43Z

← Older revision		Revision as of 07:59, 2 July 2019
Line 1:		Line 1:
	~~<sidebar>Sidebar: Flowcode Help Overview:Panels</sidebar>~~
	This article refers to the representation of an object drawn on either the [[System Panel]] or the [[Dashboard Panel]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.		This article refers to the representation of an object drawn on either the [[System Panel]] or the [[Dashboard Panel]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.

BenR at 16:42, 7 March 2014

2014-03-07T16:42:39Z

← Older revision		Revision as of 16:42, 7 March 2014
Line 1:		Line 1:
	<sidebar>Sidebar: ~~Concepts~~</sidebar>		<sidebar>Sidebar: Flowcode Help Overview:Panels</sidebar>
	This article refers to the representation of an object drawn on either the [[System Panel]] or the [[Dashboard Panel]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.		This article refers to the representation of an object drawn on either the [[System Panel]] or the [[Dashboard Panel]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.

JonnyW at 22:26, 12 December 2013

2013-12-12T22:26:00Z

← Older revision		Revision as of 22:26, 12 December 2013
Line 1:		Line 1:
	<sidebar>Sidebar: Concepts</sidebar>		<sidebar>Sidebar: Concepts</sidebar>
	This article refers to the representation of an object drawn on either the [[System Panel]] or the [[Dashboard Panel]].		This article refers to the representation of an object drawn on either the [[System Panel]] or the [[Dashboard Panel]]. It is aimed at readers who are looking to program components which require a degree of movement on the panel. For most uses of Flowcode ''world space'' is all that is required.

	__NOTOC__		__NOTOC__
	==Flowcodes representation of scale==		==Flowcodes representation of scale==

JonnyW: /* Scale vs Size */

2013-12-11T21:10:01Z

Scale vs Size

← Older revision		Revision as of 21:10, 11 December 2013
Line 20:		Line 20:
	However, there are a number of representations of the size of an object, and this can cause confusion.		However, there are a number of representations of the size of an object, and this can cause confusion.

	Imagine all objects start off with a size of 1x1x1 (a unit box). The ''scale'' of ~~the objects you see~~ can be thought of as ~~their~~ ''magnification'' from this unit.		Imagine all objects start off with a size of 1x1x1 (a unit box). The ''scale'' of any object can be thought of as its ''magnification'' from this unit.

	For example, take a marble. If it starts off at 1x1x1, ~~any~~ size ~~you see~~ is its scale (magnification) from this starting point. Double the scale and you will double the ''size'' of the marble. In this case, the terms '''size''' and '''scale''' are interchangeable - they mean exactly the same thing. All objects in Flowcode have a base size of 1x1x1.		For example, take a marble. If it starts off at 1x1x1, the size of the marble is also its scale (magnification) from this starting point. Double the scale and you will double the ''size'' of the marble. In this case, the terms '''size''' and '''scale''' are interchangeable - they mean exactly the same thing. All objects in Flowcode have a base size of 1x1x1.
	{\|		{\|
	\|-		\|-
Line 47:		Line 47:
	===When do we use size and when do we use scale?===		===When do we use size and when do we use scale?===
	There are no hard and fast rules, but usually we will use ''world size'' when positioning and measuring objects on the [[System_Panel\|panels]] as this is easier for us to visualise, and use ''scale'' when dealing with the maths behind a component as this is the 'raw' value used by the system. We may use the ''local size'' of an object when calculating its size in relation to other objects in the same group (so we can position one marble next to another without worrying about the scale of the bag).		There are no hard and fast rules, but usually we will use ''world size'' when positioning and measuring objects on the [[System_Panel\|panels]] as this is easier for us to visualise, and use ''scale'' when dealing with the maths behind a component as this is the 'raw' value used by the system. We may use the ''local size'' of an object when calculating its size in relation to other objects in the same group (so we can position one marble next to another without worrying about the scale of the bag).


	== Scale and rotation ==		== Scale and rotation ==

JonnyW at 20:39, 11 December 2013

2013-12-11T20:39:02Z

← Older revision		Revision as of 20:39, 11 December 2013
Line 22:		Line 22:
	Imagine all objects start off with a size of 1x1x1 (a unit box). The ''scale'' of the objects you see can be thought of as their ''magnification'' from this unit.		Imagine all objects start off with a size of 1x1x1 (a unit box). The ''scale'' of the objects you see can be thought of as their ''magnification'' from this unit.

	For example, take a marble. If it starts off at 1x1x1, any size you see is its scale (magnification) from this starting point. Double the scale and you will double the ''size'' of the marble. In this case, the terms '''size''' and '''scale''' are ~~interchangable~~ - they mean exactly the same thing. All objects in Flowcode have a base size of 1x1x1.		For example, take a marble. If it starts off at 1x1x1, any size you see is its scale (magnification) from this starting point. Double the scale and you will double the ''size'' of the marble. In this case, the terms '''size''' and '''scale''' are interchangeable - they mean exactly the same thing. All objects in Flowcode have a base size of 1x1x1.
			{\|
			\|-
			\| [[File:Eg Marble.png\|thumb\|none\|Marble at unit scale\|50px]]
			\| [[File:Eg Marble.png\|thumb\|none\|Marble at double scale\|100px]]
			\|}

	===Local size===		===Local size===
Line 28:		Line 33:

	The '''scale''' of the bag (its magnification) is 1:1. But its '''size''' is dependant on the number and size of the marbles inside it. In the case of the bag, size and scale are ''not'' the same. We refer to the size of the bag when considering everything inside it as its ''local size''.		The '''scale''' of the bag (its magnification) is 1:1. But its '''size''' is dependant on the number and size of the marbles inside it. In the case of the bag, size and scale are ''not'' the same. We refer to the size of the bag when considering everything inside it as its ''local size''.
			{\|
			\|-
			\| [[File:Eg Marblebag.png\|thumb\|none\|Marble bag at unit scale\|100px]]
			\| [[File:Eg Marblebag.png\|thumb\|none\|Marble bag at double scale\|200px]]
			\|}

	===World size===		===World size===
	Now, it is worth noting that although doubling the scale of the bag will appear to us to double the size of all the marbles in it, in relation to each other they are still the same. Following the definition of ''local size'' above (so consider the scale of the ~~object~~ and everything in it) none of the marbles sizes have changed.		Now, it is worth noting that although doubling the scale of the bag will appear to us to double the size of all the marbles in it, in relation to each other they are still the same. Following the definition of ''local size'' above (so consider the scale of the marble and everything in it) none of the marbles sizes have changed.

	This is clearly not true from our point of view. We see things in ''world size''. That is, the size of the object ~~when considering~~ not only everything inside it, but also the scale of ''everything it is in''. Double the scale of the bag and you double the ''world size'' of the marbles ''and'' the bag.		This is clearly not true from our point of view. We see things in ''world size'', so doubling the scale of the bag doubles the size of everything in it. That is, the ''world size'' of the object considers not only the scale of an object and everything inside it, but also the scale of ''everything it is in''. Double the scale of the bag and you double the ''world size'' of the marbles ''and'' the bag.


			===When do we use size and when do we use scale?===
			There are no hard and fast rules, but usually we will use ''world size'' when positioning and measuring objects on the [[System_Panel\|panels]] as this is easier for us to visualise, and use ''scale'' when dealing with the maths behind a component as this is the 'raw' value used by the system. We may use the ''local size'' of an object when calculating its size in relation to other objects in the same group (so we can position one marble next to another without worrying about the scale of the bag).

JonnyW at 20:18, 11 December 2013

2013-12-11T20:18:42Z

← Older revision		Revision as of 20:18, 11 December 2013
Line 16:		Line 16:

	== Scale vs Size==		== Scale vs Size==
	~~The scale factors of an object describes~~ its ~~dimensions without considering any child objects~~, ~~and as such will not be affected if any other object on the panel changes its location, size or orientation~~.		For all its internal maths, Flowcode deals with ''scale''.

	~~The ''absolute~~ size'' of an object can ~~be thought of as the product of its scale multiplied by all its child scales~~.		However, there are a number of representations of the size of an object, and this can cause confusion.

	~~This can be thought of as the~~ size of ~~the bounding~~ box of the ~~object. This~~ can be ~~read through the API call [[API Panel.Position.GetBox\|GetBox]]~~.		Imagine all objects start off with a size of 1x1x1 (a unit box). The ''scale'' of the objects you see can be thought of as their ''magnification'' from this unit.

	~~Unlike~~ scale, the ''size'' of ~~an object depends on~~ the ~~children~~ of ~~that object~~. ~~Though it may be more intuitive to think~~ of size ~~instead~~ of ~~scale~~, and ~~therefore~~ size is ~~used~~ in the ~~properties pane, internally~~ and in the ~~exposed [[API Panel~~.~~Position\|API]] Flowcode uses~~ scale~~, as this~~ is ~~much quicker to calculate~~ and ~~easier to control~~.		For example, take a marble. If it starts off at 1x1x1, any size you see is its scale (magnification) from this starting point. Double the scale and you will double the ''size'' of the marble. In this case, the terms '''size''' and '''scale''' are interchangable - they mean exactly the same thing. All objects in Flowcode have a base size of 1x1x1.

			===Local size===
			OK, so if they are the same, why do we need them both? This relationship holds OK for the marble, but now imagine you have a handful of marbles and you put them all in a bag.

			The '''scale''' of the bag (its magnification) is 1:1. But its '''size''' is dependant on the number and size of the marbles inside it. In the case of the bag, size and scale are ''not'' the same. We refer to the size of the bag when considering everything inside it as its ''local size''.

			===World size===
			Now, it is worth noting that although doubling the scale of the bag will appear to us to double the size of all the marbles in it, in relation to each other they are still the same. Following the definition of ''local size'' above (so consider the scale of the object and everything in it) none of the marbles sizes have changed.

			This is clearly not true from our point of view. We see things in ''world size''. That is, the size of the object when considering not only everything inside it, but also the scale of ''everything it is in''. Double the scale of the bag and you double the ''world size'' of the marbles ''and'' the bag.

	~~When considering '''world''' size, not only the objects children are considered, but also its parents scale. This is the bounding box of the object multiplied by all its parents scales.~~

	== Scale and rotation ==		== Scale and rotation ==

ReeceL at 11:56, 29 August 2013

2013-08-29T11:56:41Z

← Older revision		Revision as of 11:56, 29 August 2013
Line 1:		Line 1:
	<sidebar>Sidebar: Concepts</sidebar>		<sidebar>Sidebar: Concepts</sidebar>
	This article refers to the representation of an object drawn on either the [[System Panel]] or the [[Dashboard Panel]].		This article refers to the representation of an object drawn on either the [[System Panel]] or the [[Dashboard Panel]].
			__NOTOC__
	==Flowcodes representation of scale==		==Flowcodes representation of scale==