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
It would be handy if CartesianCoordinates, Text, Functions, and VectorFields were affected by Transform.
CartesianCoordinates, VectorFields, and both Function types are currently not supported simply because they use the "pane context", which is Mafs' way of not computing offscreen elements. All these components only render roughly the area you're looking at. However, I'm no wizard and I feel like the linear algebra involved in doing the lazy evaluation in a transformed coordinate space would be really tough.
Text is not transformed just because I figured people would want to preserve the legibility of the text and only transform the anchor point. We could definitely transform the text itself though (or make it an option). Maybe something like <Text transformBehavior="anchor|distort" /> or something.
The text was updated successfully, but these errors were encountered:
It would be handy if CartesianCoordinates, Text, Functions, and VectorFields were affected by
Transform
.CartesianCoordinates, VectorFields, and both Function types are currently not supported simply because they use the "pane context", which is Mafs' way of not computing offscreen elements. All these components only render roughly the area you're looking at. However, I'm no wizard and I feel like the linear algebra involved in doing the lazy evaluation in a transformed coordinate space would be really tough.
Text is not transformed just because I figured people would want to preserve the legibility of the text and only transform the anchor point. We could definitely transform the text itself though (or make it an option). Maybe something like
<Text transformBehavior="anchor|distort" />
or something.The text was updated successfully, but these errors were encountered: