Separate :class:.Animation
and :class:.Scene
#3685
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Scene
in anAnimation
.AnimationProtocol
.Implementation
TL;DR: an
Animation
stores what actions it wants to do to the Scene. During the start of the animation and end of animation, theScene
checks those actions and applies them.Long Explanation: attached to each
Animation
object is abuffer
attribute (of typeSceneBuffer
: you can think of this as an extremely simplified proxy ofScene
that storesadd
andremove
operations). Whenever an animation wants to, say add a mobject to the scene they would doself.buffer.add(Square())
.For each animation in a
self.play
call, theScene
will call the begin method and then "apply the buffer". It is at this time that the adding/removing of mobjects actually happens. Likewise with when the animation finishes.TODO
SceneBuffer
stuffAnimationProtocol