View
A View sitsis abovea Scenehierarchically inhigher theconcept hierarchy:than youa Scene. You can treat a single Scene as one screen, or groupcombine multiple Scenes and/or existing Views into a single screen state.state (Composite View). Each View isrepresents a logical unit that specifiesdefines what content tois displaydisplayed and how to display it on a givenspecific screen.screen, Onand the engine side, Views areis identified by thea dedicated identifier type called ViewIdentifier. on the engine side.
To use a Scene directly as a View, set the Scene's IsView property to true. A ViewScene with IsView=true can be referenced as is authored— primarily inas the transition target of Jump to View, Definitionas Editora component of a Composite View, and theas resulta isView output target during asset generation. The following two types are candidates that can be referenced as a commonView:
The system handles View show/hide automatically as internal processing, so you do not need to configure display control elements directly. In the View Tree, the State Machine, and the Action Chain Editor. Screen showing and hiding is handled automatically as part of internal processing, so users do not need to configure display-control elements directly. In the View Tree, you define the transition structure betweenof multiple Views as a tree, and thisthe system outputs that information is exported as a Global State Machine asset. Furthermore, byBy combining the Action Chain Editor andwith the Condition Editor, you can design view-level screen transitions and event logic thatper respondView tobased on input devices and theor solution state.states.
By introducing Views,Views in this way, you can keepseparate Scene-level layout definitions separate from screen-level transition/transition and control logic, whileand organizingorganize and maintainingmaintain the solution’entire solution's overall screen composition consistently at the View level.
CreateCreating a View (fromUsing a Scene)Scene Directly as a View)
WhenTo youuse createa Scene as a View startingon fromits own, set the Scene's IsView property to true. This makes the Scene referenceable as a Scene,View thatwithout Scenegoing isthrough automaticallya associated with the newly created View. You can use it immediately as theseparate View that displays that Scene.object.
In the Solution
Explorer,Explorer, selectanythe target Scene.
The
asAddScene becomes referenceable as aNewJump To Viewdialogtarget,opens.
Configure the required settings and click OK.
The valueScene set in Namename is used as the View’s display name in Solution Explorer.
The same value is also assigned automatically as the View Identifier.
With this method, the Scene itself is treated as a View. Because the Scene name and the View name match, you can keep the entire solution's namespace tidy.
Creating a View (Composite View)
To create a new Composite View that combines multiple Views, first create an empty View item, and then add the component Views inside the View Definition Editor.
This operation automatically establishes the association between thecreated View andto the Scene.
Create a View (New Item)
If you create an empty View, you must later add and associate Scenes inopen the View Definition Editor., Thisand methodadd letsScenes youwith flexiblyIsView=true buildor compositeother Views that combine multiple Scenes.
In Solution Explorer, open the context menu at the desired location and choose Add > New Item.
From the left menu, select View.
The View settings appear on the right.
Configure the required settings and click OK.
The value set in Name is used as the View’s display name in Solution Explorer.
The same value is also assigned automatically as the View Identifier.
A new View is created in Solution Explorer.
BecauseA aComposite View created by this methodway hasis noa Scenescreen-level associatedView yet,that youbundles needmultiple todisplay addelements, and can be referenced from the Scene(s) you want to display later in the View DefinitionTree Editor.and Action Chain Editor.