You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Technically all animation attributes are children of the element they apply to. But for memory reasons I don't want to make any SVGNode that supports being animated a container element. Instead the AttributeNode which only exists during load time should keep the animation elements.
Then before building an element we would parse the animation elements. This way when an element request the say width property from the AttributeNode it could instead of returning a plain Length return an animation capable substitute.
The current animation time would be passed in the MeasureContext s.t. the animation attributes can properly be resolved while rendering.
The text was updated successfully, but these errors were encountered:
I have an implementation ready that currently supports animation of length values for basic shapes.
Bringing animation support to all animatable properties will be a long process. Therefore it would be great to get some feedback on what sorts of properties are of interest here. Simply respond with this issue what you would like to be prioritised. If possible an example SVG would be highly appreciated.
Technically all animation attributes are children of the element they apply to. But for memory reasons I don't want to make any
SVGNode
that supports being animated a container element. Instead theAttributeNode
which only exists during load time should keep the animation elements.Then before building an element we would parse the animation elements. This way when an element request the say
width
property from theAttributeNode
it could instead of returning a plainLength
return an animation capable substitute.The current animation time would be passed in the
MeasureContext
s.t. the animation attributes can properly be resolved while rendering.The text was updated successfully, but these errors were encountered: