# View Definition Editor

**View Definition Editor** lets you define “screen-level Views” by combining Scenes created in SceneComposer with existing [**<span style="color: rgb(230, 126, 35);">Views</span>**](https://doc3161en.candera.eu/books/view-editor/page/view), and make those definitions available to the **<span style="color: rgb(230, 126, 35);">[View Tree](https://doc3161en.candera.eu/books/view-editor/page/view-tree)</span>**, the **State Machine**, and the <span style="color: rgb(230, 126, 35);">[**Action Chain Editor**](https://doc3161en.candera.eu/books/view-editor/page/action-chain-editor)</span>.

Only **Views** appear as nodes in the tree of the **View Definition Editor** panel. A Scene with **IsView=true** can be referenced as a View on its own, so when you want to compose a screen from a single Scene, you can place that Scene directly as a View. When you want to build a screen that bundles multiple display elements, create a **Composite View** and combine **Scenes with IsView=true** or other Views as its components. For details, see <span style="color: rgb(230, 126, 35);">[**View composition**](#bkmrk-view-composition)</span> later in this document. With this structure, the state machine can consistently treat “which screen (View) to activate” at the View level, while still incorporating Scene-based content into the screen composition.

### View Definition Editor UI 

#### Panel layout

Double-click any **View** in **Solution Explorer** to open the **View Definition Editor** panel.

<div drawio-diagram="9003"><img src="https://doc3161en.candera.eu/uploads/images/drawio/2026-05/drawing-4-1779257978.png" alt=""/></div>

<table border="1" id="bkmrk-ui-item-description-" style="width: 800px; height: 198.92px; border-collapse: collapse;"><thead><tr style="height: 29.7017px;"><th style="width: 276.009px; background-color: rgb(35, 111, 161);">**<span style="color: rgb(255, 255, 255);">UI item</span>**</th><th style="width: 523.082px; background-color: rgb(35, 111, 161);">**<span style="color: rgb(255, 255, 255);">Description</span>**</th></tr></thead><tbody><tr style="height: 46.5057px;"><td style="width: 276.009px; height: 46.5057px;">**View Composition pane** (orange frame in the figure above)

</td><td style="width: 523.082px; height: 46.5057px;">Lists which **Scenes/Views** the selected **View** is composed of. Add or remove Scenes and existing Views by **drag and drop**.

</td></tr><tr style="height: 46.5057px;"><td style="width: 276.009px; height: 46.5057px;">**Preview area** (red frame in the figure above)

</td><td style="width: 523.082px; height: 46.5057px;">Displays preview images of the **Scenes/Views** associated with the View in the right pane, where you can also adjust their layout positions. Useful for improving visual identification when referencing this View from the **State Machine** or **View Tree**.

</td></tr></tbody></table>

<article class="text-token-text-primary w-full focus:outline-none [--shadow-height:45px] has-data-writing-block:pointer-events-none has-data-writing-block:-mt-(--shadow-height) has-data-writing-block:pt-(--shadow-height) [&amp;:has([data-writing-block])>*]:pointer-events-auto scroll-mt-[calc(var(--header-height)+min(200px,max(70px,20svh)))]" data-scroll-anchor="true" data-testid="conversation-turn-260" data-turn="assistant" data-turn-id="ff8c5c17-5101-4c8d-b97a-17a581ab08ff" dir="auto" id="bkmrk-basic-operations-thi" tabindex="-1">### Basic operations

This section outlines common procedures for defining and editing Views with the **View Definition Editor**.

<p class="callout info">For instructions on creating a **View**, see the <span style="color: rgb(230, 126, 35);">[View feature overview page](https://doc3161en.candera.eu/books/view-editor/page/view)</span>.</p>

#### View composition

</article>In the **View Definition Editor** panel, you can use the tree structure to edit or delete child Views under the currently opened View. You can also review the entire tree rooted at that View on the tree, including the hierarchical relationships of its child Views and their descendant Views.

<p class="callout info">The composition editing described here applies to Views created as Composite Views. A Scene with IsView=true is treated as a standalone single-screen View, so you cannot edit its tree structure or add child elements in the View Definition Editor (it is always treated as a leaf node).</p>

1. In the Solution Explorer, double-click the **View** (Composite View) whose composition you want to edit.
2. In the View composition pane, edit the elements to include in the View. 
    - You can drag and drop a **Scene with IsView=true** or an existing View from the Solution Explorer to add it.
    - To remove an unnecessary element, select it and then select **Delete** from the context menu.

##### Behavior When You Drag and Drop a Scene with IsView=true

Only **Views** appear as nodes in the tree of the View Definition Editor panel. However, because a Scene with **IsView=true** is treated as a View on its own, you can add it directly to the tree.

- When you drag and drop a Scene with **IsView=true** from the Solution Explorer onto the composition pane of the Composite View open in the View Definition Editor, the Scene is added as a child element.
- A Scene with **IsView=false** is not included as a View candidate, so you cannot drag and drop it onto the composition pane. You must first select **IsView** in the Properties panel.

With this mechanism, the View Definition Editor tree can consistently treat the unit of screen transitions and visibility control as **Views**, while still allowing you to build Scene-based content within those Views.

##### Grandchild View

In the View Definition Editor panel, a single operation can add only "a child View one level below the View you have opened." To build structures with three or more levels — such as parent View &gt; child View &gt; grandchild View — start from a **Composite View** (a View that bundles multiple Views).

- Place **Composite Views** at the parent and intermediate levels (because they are not leaf nodes, they can hold child Views beneath them).
- A **Scene with IsView=true** is always treated as a leaf node and cannot be used as an intermediate node in a grandchild hierarchy.

Using a View that meets these requirements as the starting point, create a three-level structure (**Parent View &gt; Child View &gt; Grandchild View**) as follows:

1. Open the View you want to use as the parent level, and add a child View under it (**Parent View &gt; Child View**).
2. Double-click the View you added as the child View in step 1 to open it, and then add another View under it as its child (**Child View &gt; Grandchild View**).

After performing these steps, reopen the original parent View. You can then confirm in the tree that a three-level hierarchy (**Parent View &gt; Child View &gt; Grandchild View**) is displayed.