Closed liquidcronos closed 2 years ago
This is proably best resolved by folding the transformation matrix class into the transformation class and extending its functionality accordingly to offer translation and rotation directly
Combining them would also simplify the interfaces since transformation conventions are currently defined in two places
one would expect the output of composite transformation matrices to be a a array not a matrix. This is because while it is possible to multiply transformationmatrix objects their main functionality no longer properly functions in this case.