====== Object ======

As this is a very simplified documentation, we may retreat to the following statement: while 'primitive' values - like [[string|strings]], [[single|singles]] etc. - contain only one value, objects are more complex. A very basic example is given in the [[macros:types|overview on types]]: imagine an address which is composed maybe of a street name, a number, a zip code, and a city - then the whole thing is the address object, and the individual values are the properties of this object.

In the context of Titan macros, you'll most likely see objects like [[..:identifier:handle|handles]], [[.object:timestamp|timestamps]], and some more. They are explained in more detail in separate articles - see the indivitual link further down.

Also, there seems to happen implicit parsing/conversion. E.g. the function [[macros:function:math.min]] expects two objects as input - but in the example [[macros:example:doublechasespeed]] it also works with a number like 3600.0:

<code xml>
<step>Math.Min("Playbacks.Editor.Times.ChaseSpeed", Playbacks.Editor.Times.ChaseSpeed * 2, 3600.0)</step>
</code>

Example for the use of objects: [[macros:function:actionscript.setproperty]]:

  ActionScript.SetProperty(String id, Object value)

This sets a particular property, identified by its id, to an object value.

More specifically, as mentioned there,

<code xml>
<step>ActionScript.SetProperty("Handles.SourceHandle", Playbacks.Editor.SelectedPlayback)</step>
</code>

sets the property named ''"Handles.SourceHandle"'' to be the multidimensional object value ''Playbacks.Editor.SelectedPlayback''.

You can find some details about the properties which are used in the [[macros:properties_list|overview about properties]].

== object types in this Wiki ==

<nspages macros:type:object -h1 -simpleList -textPages="">
However the most important object type in Titan is more in-depth explained as [[macros:identifier:handle]].

== Objects are also mentioned in ==

{{backlinks>.}}


~~DISCUSSION~~