Animation Order In most cases, ^In and ^Loop, ^Update, ^Out are all you will need. Revealing initial data A series of animations are played to reveal the first record. Order | Scene Director Tag | Description |
|---|
1 | ^Reset |
| This Scene Director is never played, but is positioned to key 0 before the scene goes online, allows a spot to reset any properties that may have been altered by other animations. Very useful for scenes that support various states. | 2 | ^ZoneIn | Used to animate the Zone on. Used if many scenes have the same Background. Unlike a Background/Bug scene, this Zone may have a specific tag (ie: ^Subtopic or ^City). | 3 | ^In | The second Scene Director played (after ZoneIn). It is intended to reveal objects that will remain visible while the scene is online. | 4 | ^LoopOn | The Time between the ^In and ^ContentIn | 5 | ^ContentIn | This controller is used to display the first data entry, as well as any subsequent data reveals if the ^Update animation is not used. If no Content included in the ^In tag, this scene is used after the ^LoopON duration | 6 | ^FirstLoop | The duration between ^In or ^ContentIN and ^PageTwo | 7 | ^PageTwo | Alt page before repetition of content | 8 | ^Loop | Duration of all your Scenes. Also used to reset from A state to B state |
Revealing remaining pages If there is more data to display, only animate the components that have more data using: ^NextPage + ^MoreDataOn/^EndDataOn Order | Scene Director Tag | Description |
|---|
1 | ^NextPage | Paging of your content if "word wrap" is enabled in your object | 2 | ^MoreDataOn | Unlike paging, this animation controller displays more content without removing. | 3 | ^EndDataOn | |
Revealing the next record There are three methods for showing the next record: the Update Method, Off/On Method, and the Scroll Method Update Method ^Update, ^Loop The update method is the recommended method for transitioning between data records. It required that requires there be a "Version B" copies copy of each object, and the ^Update animation will transition from showing "Version A" of the objects to showing "Version B". e.g. ^Story will be visible initially, but by the end of the animation, ^StoryB is visible and ^Story is hidden. The additional requirement with this implementation is that the ^Loop animation resets the keyframes for the A/B versions on the first keyframe. This will appear transparent to the viewer. e.g. At t=0 ^Story will be made visible and ^StoryB will become hidden. Order | Scene Director Tag | Description |
|---|
1 | ^Update | Going from Story 1 to Story 2 of the same topic | 2 | ^Loop | Duration of all your Scenes. Also used to reset from A state to B state |
Off/On Method ^ContentOut, ^ContentIn, ^FirstLoop, ^PageTwo, ^Loop This method only requires one copy of each object, but will cause a brief period where there is no content on air as it prepares the next record. The current content is animated off using the ^ContentOff animation, then the new data is applied before starting the ^ContentIn animation. Order | Scene Director Tag | Description |
|---|
1 | ^ContentOut | Animates the current Item OFF, but keeping the BG ON | 2 | ^ContentIn | Animates the new item ON | 3 | ^FirstLoop | The duration between ContentIN and PageTwo | 4 | ^pageTwo | 2nd part of the new item | 5 | ^Loop | Duration between new item and next item |
Scroll Method If the scene is a Scene Group, no ^Loop animation is needed. Instead, content will be continuously appended to the scroll. Removing the last record Order | Scene Director Tag | Description |
|---|
1 | ^ContentOut |
^TopicChange + ^SubtopicChange ^TopicChange is ran whenever | Removes the Content and not the background | 2 | ^LoopOFF | The duration between ContentOut and Out | 3 | ^Out | Removes both background and content (if no ContentOut) (if no Out, In is played in reverse) | 4 | ^CrawlOut | Removes the SceneGroup Parent scene. Used when a ^End scene is available in the SceneGroup |
Changing Topics and Subtopics Order | Scene Director Tag | Description |
|---|
1 | ^TopicChange | When the kind of content (stories, weather, etc) change, but the same scene is used to display both. This allows a place to transition out any previous text/graphics and bring in new information. | 2 | ^SubtopicChange |
| When the group of content (headlines, entertainment, etc) change, but the same scene is used. This allows a place to update the heading for the current content | 3 | ^SubtopicUpdate | When the group of content AND the content changes. | 4 | ^SubtopicChangeCrawl | When the group of content AND the content changes in a crawl. Works if ^SubtopicChange child scene is available in the SceneGroup |
The order of a major sequence would be ^Reset ^ZoneIn ^In ^ContentIn ^FirstLoop ^PageTwo ^Loop ^Nextpage ^Loop ^NextPage ^Loop ^Update ^Loop ^Nextpage ^Loop ^NextPage ^Loop ^Update ^Loop ^Nextpage ^Loop ^NextPage ^Loop ^SubtopicUpdate ^Loop ^Nextpage ^Loop ^NextPage ^Loop ^Update ^Loop ^Nextpage ^Loop ^NextPage ^Loop ^Out ^Progress/^ProgressIdle These animations are ran with each record change, allowing a place to update the position/text of a progress indicator. When used in conjuction with the ^DataIndex and ^DataCount objects, it provides a way to use scripting to animate progress. Animation Descriptions Below we will explain the specifics of what each one is responsible for. This animation controller is never played, but is positioned to key 0 before the scene goes online, allows a spot to reset any properties that may have been altered by other animations. Very useful for scenes that support various states. The first animation controller played, it is intended to reveal static objects that will remain visible while the scene is online. ^ContentInThis controller is used to display the first data entry, as well as any subsequent data reveals if the ^Update animation is not used. Body text here. |