Repository navigation
char_* presets: rotate_from, scale/baseline jitter, reflow (undelivered parts of #363) #429
Description
Activity
All three items are on
CharAnimationTimingonmain—rotate_from/rotate_origin,scale_jitter/baseline_jitterwithseed, andreflow/reflow_easing(merged in #450).The two gaps #450 asked to be read before closing are both resolved, each the way the repository rule allows — a field the validator accepts must have an effect, or the validator rejects it or warns:
reflowonrich_textis named rather than silently inert.check_reflow_reaches_this_component(merged in fix(validate): stop the false positives, name the right edge, warn once #449) emitsreflow has no effect on rich_text, because that component's char animation lays out from token positions it precomputes independently.reflowontypewriteris rejected outright, verified just now:unknown fieldreflow, expected one ofdelay,duration,loop, …, and the component is refused rather than silently dropped.AnimationEffect::Typewritercarries a bareAnimationTiming, and puttingreflowthere would make it inert on every other preset — the same violation, moved.
Whether
typewritershould gain real reflow is a feature question, not this issue's unfinished business: #450 recorded that the original complaint did not reproduce. Open a new issue if a scenario shows it.
Context
#363 was closed after fixing char_* on
rich_text/gradient_text, but three requested capabilities were not delivered and are rejected as unknown fields.rules/char-animation-rich-and-gradient-text.mdonly notes them as absent.To do
rotate_from(+rotate_origin): each unit starts tilted and straightens while it settles (staircase word reveal).scale_jitter/baseline_jitterwithseed: deterministic per-unit size and baseline variation (letters born at different sizes, then aligning).reflow/reflow_easingon char_* presets andtypewriter: a centred line stays centred while it is being written, instead of growing from a fixed left edge.Definition of done
mainis written first. For anything visual it is a render test (scenario → frame → pixel assertions); tests that buildAnimatedPropertiesby hand are not enough — that is exactly how the regressions listed here slipped through.rustmotion validate, render, image inspected.cargo fmt --all --check,cargo clippy --workspace --all-targets -- -D warnings,cargo test --workspacepass.crates/rustmotion/skills/SKILL.md, the relevantrules/file and the exported schema. A field the validator accepts must have an effect, otherwise the validator rejects it or warns.<type>: <verb> <message>. No AI attribution in commits, PRs or issue comments.