What problem does it solve?
Developers and documenters working with the Gum UI tool lack a clear reference for how the editor's Animations tab works internally, including its StateAnimationPlugin architecture, .ganx sidecar persistence, and the confusing three-way keyframe union model.
Core Features & Use Cases
- Architecture Mapping: Explains the MEF plugin structure (StateAnimationPlugin), the View/ViewModel hierarchy, and where animation data lives relative to element files.
- Data Model Reference: Details the ElementAnimationsSave/AnimationSave serialization format, cumulative state keyframes, and the "Category/State" naming convention.
- Pitfall Documentation: Clarifies that named events are FlatRedBall-only, that InterpolationType comes from the FlatRedBall.InterpolationCore NuGet package, and that state animations differ from runtime AnimationChains.
- Use Case: When writing documentation or fixing a bug where renaming a Gum element loses its animations, consult this Skill to learn the .ganx sidecar must be moved via RenameManager.
Quick Start
Explain how the Gum editor's Animations tab saves keyframes and why my element's animations disappeared after renaming it.