mcrfpy.Color and mcrfpy.Vector animation targets #218
Labels
No labels
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
priority:tier4-deferred
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:procgen
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
john/McRogueFace#218
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We can animate an object's
xandypositions separately, but this feels hacky. We could animate aposto a new value. It would even be OK for the animation system to break this down into anxandyanimation internally, as long as we handle the callback correctly (we wouldn't want to callback after one property finishes but the other still has a frame to go, for instance).The same applies to
r,g,b, andaproperties on a color.This ties into the concept of "animation groups", which would only trigger their callback when all animations were completed; but it's somewhat simpler because it doesn't have to support multiple duration values within the group.