These do not account for skew, we would have to look at including (perhaps?) a matrix for each object instead of separate properties, though I’m concerned about performance. This should be a start for taking a look
Taking another look, it appears that right now, the display list is using x, y, scaleX, scaleY and rotation separately, it is not maintaining a matrix per object. There is a “world transform” that is a matrix, which is updated from the above properties as needed.
That means that as a downside, using the transform.matrix property, you should be able to skew, this not handled currently. It looks like we are going to need to test an architecture that uses a matrix per object (and sets this when using rotation, scaleX, scaleY, etc) rather than separate properties
OK,
After a bit of playing around with the beta, this seems to work really good.
already tried it on a few moderately complex projects in Android and HTML5
for now i see that it fixed that issue!
Thanks for the update…!
2 questions if i might be a bit bold
Will it be included in the next update?
If so, is there an approximate release date for this update?
The plan is to include it in the next release, releases happen in a week or two, but usually it has to do with how stable I feel the code is, so I want to make sure we don’t introduce regressions in setting and getting scaleX/scaleY/rotation or introduce render bugs or mouse coordinate related issues due to this change