# Scene2D Objects

**Scene2Ds** also have several **Objects**. "**Object**" is a broad term used to describe a number of different components, each with their own purpose, behaviors, and characteristics.

For in-depth descriptions of each type of **Object**, see the [**Table of Contents**](#contents) below.

## Managing Objects

**Objects** in a **Scene2D** are managed in the **Scene Outliner**. There they can be created, deleted, edited, and organized. For more detail, see the [**Scene Outliner**](/incari-studio/2022.2/modules/scene-outliner.md) section. They are effectively the same processes that govern **Scene Objects**.

![Objects in a Scene are managed in the Scene Outliner.](/files/Drfb1aQMYsmKBWSRUdwB)

## Attributes

**Attributes** define specific characteristics of entities in **Incari** and can be modified in the [**Attribute Editor**](/incari-studio/2022.2/modules/attribute-editor.md). Particularly, there are several sets of **Attributes** that are shared throughout **Objects**. These are explained in detail in the [**Common Attributes**](/incari-studio/2022.2/objects-and-types/attributes/common-attributes.md) section:

* [`Object`](/incari-studio/2022.2/objects-and-types/attributes/common-attributes/object.md): The `Name`, `Type`, and `Opacity` of an **Object** are shown here.
* [`Tag`](/incari-studio/2022.2/objects-and-types/attributes/common-attributes/tag.md): *Metadata* that serves as an identifier for an **Object** or several of them.
* [`Transformation`](/incari-studio/2022.2/objects-and-types/attributes/common-attributes/transformation.md): They define the *position* and *rotation* of an **Object** in a **Scene2D**.

![Object Attributes.](/files/NE8onngWcmUFohIe6Wvu)

![Tag Attributes.](/files/v78aZyoO4xHt4npAb4Mm)

![Transformation Attributes.](/files/cwpUGMvQBFHxQDlERkbH)

### Structure in a Scene

As in **Scenes**, **Objects** in **Scene2Ds** fall under a certain hierarchy. All **Objects** are children of the [**Root Object**](#root-object), but only one **Object** type can be a *parent* itself. These are **Frames**. No other **Objects** can contain *children* in **Scene2Ds**.

### Root Object

Every **Scene2D** has a **Root Object**, which is the *parent* of all **Objects** that are on the first hierarchy level. Thus, all **Objects** in a **Scene2D** are *descendants* of the **Root Object**. To obtain the **Object ID** of the **Root Object**, use the [**Get Root** **Node**](/incari-studio/2022.2/toolbox/incari/object/get-root.md).

### Nodes

There are a few **Nodes** that allow the user to obtain and use information about the structure of **Objects** in a **Scene2D**. These are:

* [**Get Children**](/incari-studio/2022.2/toolbox/incari/object/get-children.md): Returns the *children* of an **Object**.
* [**Get Parent**](/incari-studio/2022.2/toolbox/incari/object/get-parent.md): Returns the *parent* of an **Object**.
* [**Has Children**](/incari-studio/2022.2/toolbox/incari/object/has-children.md): Returns a **Boolean** indicating whether an **Object** has *children*.

For more information about *trees*, visit the [Tree (data structure)](https://en.wikipedia.org/wiki/Tree_\(data_structure\)) page on *Wikipedia*.

## Contents

* [**GUI**](/incari-studio/2022.2/objects-and-types/scene2d-objects/gui.md)
* [**Vector**](/incari-studio/2022.2/objects-and-types/scene2d-objects/vector2d.md)
* [**Camera**](/incari-studio/2022.2/objects-and-types/scene2d-objects/camera2d.md)
* [**Frame**](/incari-studio/2022.2/objects-and-types/scene2d-objects/frame.md)
* [**Image**](/incari-studio/2022.2/objects-and-types/scene2d-objects/image.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.incari.com/incari-studio/2022.2/objects-and-types/scene2d-objects.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.