Add: global factor controlling fps base interval
This commit is contained in:
@@ -10,6 +10,7 @@ P2
|
||||
|
||||
Standardize `sprite.png` packs so each of the 7 rows maps to semantic animation groups, while
|
||||
keeping runtime compatibility with existing state names (`active`, `success`, `error`).
|
||||
Also retune 8-frame animation tempo to a slower profile for readability.
|
||||
|
||||
## Scope
|
||||
|
||||
@@ -42,6 +43,16 @@ One-shot defaults:
|
||||
2. All bundled sprite-pack manifests now expose row-based names and compatibility aliases.
|
||||
3. Added runtime-core unit test to confirm `SetState::Dragging` selects `"dragging"`.
|
||||
4. Updated schema/design docs to formalize the row convention.
|
||||
5. Retuned bundled pack fps profile:
|
||||
- loops: `1` fps
|
||||
- one-shot `celebrate` and `success`: `2` fps
|
||||
6. Tauri renderer-level pacing adjusted:
|
||||
- added global frame interval slowdown factor (`x2`) in Pixi ticker to further reduce perceived speed
|
||||
without changing manifest schema type (`fps` remains integer).
|
||||
7. Added persisted tauri slowdown factor control:
|
||||
- config key: `frontend.tauri_animation_slowdown_factor` (integer, range `1..20`, default `3`)
|
||||
- new tauri commands/events to read/update factor at runtime
|
||||
- settings window slider added for live tuning and persistence.
|
||||
|
||||
## Verification
|
||||
|
||||
|
||||
Reference in New Issue
Block a user