ID:1951290
 
Applies to:
Status: Open

Issue hasn't been assigned a status value.
DM has adopted transform matrices for the icon with all other base processes other than Skew. I understand Skew can already be performed with Turn and Scale play, but it's much less efficient than if the core engine had its own process.

Thoughts?
The affine transforms currently supported in icon math are kind of limited. (In fact, I'd love to implement something like RotSprite to handle rotations.) But with the frontend transform options, I don't really see a lot of point in implementing skew.