As this is a very simplified documentation, we may retreat to the following statement: while 'primitive' values - like strings, singles etc. - contain only one value, objects are more complex. A very basic example is given in the 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 handles, timestamps, and maybe some more. While by their nature they fall under the general class 'objects', they are that frequently used - and thus that important for us - that we explain them as separate types (which is how they are treated in most funtions' description, too).

Example for the use of objects: 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,

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

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 overview about properties.