SL23W32: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
**Rule: Very limited set of pdas for stages | **Rule: Very limited set of pdas for stages | ||
**Rule: Each variant has same nmsids to make sure spawn/destroy works | **Rule: Each variant has same nmsids to make sure spawn/destroy works | ||
**'''Rule: Layout creation needs a lot of validation checks to make sure these rules are applied''' | **'''Rule: Layout creation needs a lot of validation checks to make sure these rules are applied''' | ||
*Hide most pda actions by default for now | *Hide most pda actions by default for now | ||
*'''Auto-generate missing Variants for parts of a layout if not existing'''<br /> | *'''Auto-generate missing Variants for parts of a layout if not existing''' | ||
*'''Try if we can add a transition on to a stage fake and combine that with the transition state of the child'''<br /> | |||
<br /> | <br /> | ||
Revision as of 18:08, 17 August 2023
- Renaming of "Scenes" to "Layout" as it is to close to Screen/Scene/Stage
- Implement Pda "TransitionStage" that gets generated from a transition when a layout is created.
- Rule: Transitions are needed in each element
- Rule: Interpolation-Duration can differ for elements
- Rule: NMS needs to be created for all variants (lazy creation possible)
- Rule: Only allow in-order-transitions (V1 -> V2 -> V3 ...) in stages
- Rule: Very limited set of pdas for stages
- Rule: Each variant has same nmsids to make sure spawn/destroy works
- Rule: Layout creation needs a lot of validation checks to make sure these rules are applied
- Hide most pda actions by default for now
- Auto-generate missing Variants for parts of a layout if not existing
- Try if we can add a transition on to a stage fake and combine that with the transition state of the child