# CGI Studio 3.4.0.1

# SceneComposer V3.4.0.1

# SceneComposer Usability Improvements

#### Easy Mode Generator

A configuration file will allow the user to set values that will overwrite the default value from the ApplicationConfig file when SceneComposer starts. This file can be generated by using the "SceneComposerConfigurator.exe".

In this way, it can be set which object properties are to be presented in SceneComposer's property grid, "Preferences", and all existing dynamic properties (Polarion CGI1-15841, CGI-15842 & CGI-16101).

The configuration file will contain an element "Commands" containing the element "ForbidControlCreation" (Polarion CGI1-17441). The element "ForbidControlCreation" can contain only values "True" or "False" were:

<div class="contents" id="bkmrk-true%3A-scenecomposer-"><div class="contents"><div class="textblock">- True: SceneComposer no longer allows creating new controls
- False: no behavioral change in SceneComposer

</div></div></div>The configuration applies to all static object properties. The user can rule for dynamic properties like widgets, behaviours, controls. The configuration of widgets, behaviours and controls cannot be extracted/generated automatically.

The configuration values which can be set are:

<div class="contents" id="bkmrk-initial-value%3B-restr"><div class="contents"><div class="textblock">- Initial value;
- Restrict visibility (True/False);
- ForeceReadOnly (True/False).

<dl class="see"><dt>**See also:**</dt><dd>- <span style="color: rgb(230, 126, 35);">[Easy Mode Generator](https://doc316en.candera.eu/link/182#bkmrk-page-title)</span> in SceneComposer User Manual

</dd></dl>---

</div></div></div>#### Transitions

The previously added feature of scene transition editor was completely re-done (Polarion CGI1-15898, CGI1-15858, CGI1-15885, CGI1-16195 etc.). Since now on two different panels are available to set and use transitions:

<div class="contents" id="bkmrk-%22rules-editor%22%3A-it-a"><div class="contents"><div class="textblock">- "Rules Editor": it allows the definition of transitions on a per scene basis and test these transitions directly in SceneComposer's display preview. The designer can use the editor to set the transitions to ("Destination") or from a scene ("Source") just by selecting or by dragging and dropping effects onto the scene list.
- "Transition Execution": supposing that the scenes are prepared to be used in a transition, the user has to choose which kind of transition will be assigned to the "Activate" and "Deactivate" state of the scene. The former concept indicates what will happen when the transition will be working from a scene **to** that scene or when will be working on a scene alone, and the latter indicates what will happen when the transition will be working **from** that scene to another one or when will be working on a scene alone. This operation can be done in a secondary panel named "Transition Execution".

</div></div></div>In addition to cut, fade, slide and scale transitions - or combinations of these - a new build-in transition type was added: Animation. By using it is possible to trigger animations or group animations within transitions.

<div class="contents" id="bkmrk-see-also%3A-transition"><div class="contents"><div class="textblock"><dl class="see"><dt>**See also:**</dt><dd>- <span style="color: rgb(230, 126, 35);">[Transitions](https://doc316en.candera.eu/books/scene-design/chapter/transitions)</span> in SceneComposer User Manual

</dd></dl>---

</div></div></div>#### Control Node Animations

SceneComposer 3.3.1 displays local animations (Control node animations) and plays them, but does not offer any possibility of including them in Animation Groups (Polarion CGI1-15885). Since this version on, the "Local animations" are renamed "Control animations". The command by add animations into an animation group has been split in two distinct and self-explanatory commands (available in the context menu):

<div class="contents" id="bkmrk-%22add-this-animation-"><div class="contents"><div class="textblock">- "Add this Animation to Animation Group(s)" and
- "Add Animations to this Animation Group".

</div></div></div>Another related features:

<div class="contents" id="bkmrk-after-a-control-anim"><div class="contents"><div class="textblock">- After a control animation is added, it behaves as any animation node. It inherits Delay and Startup properties (startup is available only in certain circumstances).
- AnimationGroup panel has been changed. Instead of displaying the name of nodes (Which is very irrelevant to the user) it now displays the full name of the animations and short version of the control animations.
- Categories for a normal animation (inside an animation group) are reorganized: a) Delay and Startup are moved to a separate category called "Animation", which is displayed after "General"; b) A new readonly property is available, "Animation" which displays the name of the node animation

<dl class="see"><dt>**See also:**</dt><dd>- <span style="color: rgb(230, 126, 35);">[Animation Groups](https://doc316en.candera.eu/books/animation-design/page/animation-groups)</span> in SceneComposer User Manual

</dd></dl>---

<dl class="see"></dl></div></div></div>