Skip to main content

Overview

View Editor is the feature set in SceneComposer for designing and managing Views. You can compose screen-level Views by combining Scenes and existing Views, structure their transitions as a tree, and export the result as a Global State Machine asset. YouIn addition, you can also visually define per-View event logic and screen transitions for each View as Action Chains, and reuse them as conditional processing based on input devices and the solution state by using the ConditionConditionOutputs Blocksdefined in ConditionBlocks created in the Condition Editor.

This page provides the View Editor feature set used to work with them. The View Editor consists of the following four panels.

For details on Views, see the View overview page.

View Definition Editor

An editor for defining screen-level Views by combining Scenes and existing Views, and for managing screen composition information. Views defined here are referenced as the common screen unit from the View Tree, the state machine, and the Action Chain Editor.
View Tree

An editor for arranging Views in the solution as a tree and designing screen transitions based on that structure. The structure you configure is exported as a Global State Machine and used as the candidate targets for the JumpToView Action behavior configured in the Action Chain Editor.
Action Chain Editor

AnThis editor forlets you visually defining, per trigger, the flowcharts ofdefine event handlingprocessing and screen transitions for a View.View Youas trigger-based flowcharts. For each View selected in the View Tree, you associate an Action Chain withand each View selected inuse View Tree, and for branching conditions you reference Condition BlocksConditionOutputs created in the Condition Editor. as branch conditions.

 
Condition Editor

The Condition Editor letsis youan editor for visually definedefining conditions asthat Condition Blocks—both the onesare evaluated inside anin Action ChainChains and the onesor assigned to the Condition propertyproperties of behaviors/Fusion.Fusion as ConditionOutputs inside ConditionBlocks. The Conditioncreated Blocks you createConditionOutputs can be reused as branchingbranch conditions in the Action Chain Editor and referenced from multiple placeslocations acrossin the solution as shared conditional logic.

 

Used together, these let you define View-based screen composition and transition logic in a consistent, unified way.

 

 

 

Back to top