Hi Armin,
Armin Le Grand schrieb am 22-Jan-20 um 18:13:
Interesting - so they do the same thing and let it look like the
coordinate system we all know from school and that rotates
counterClockWise - a good argument to mabe just stay with that in the
files. But that raises a problem with
Hi Regina,
yup. you are correct - I mixed up the full Matrix UNO API call with
stuff in aw080, sorry. More comments inline...
On 21-Jan-20 00:53, Regina Henschel wrote:
> Hi Armin,
>
> Armin Le Grand schrieb am 20-Jan-20 um 14:32:
>> Hiho,
>>
>> sorry for the late answer :-)
>>
>> History: When
Hi Armin,
Armin Le Grand schrieb am 20-Jan-20 um 14:32:
Hiho,
sorry for the late answer :-)
History: When doing deep change work quite some years ago, I did *not*
realize that rot angle and shear angle were *mirrored* - sigh. This was
probably historically the case due to the Y-Axis going
Hiho,
sorry for the late answer :-)
History: When doing deep change work quite some years ago, I did *not*
realize that rot angle and shear angle were *mirrored* - sigh. This was
probably historically the case due to the Y-Axis going down technically
in OutDev's (right-handed), but handled in
Hi Regina,
On Mon, Jan 06, 2020 at 02:35:02PM +0100, Regina Henschel
wrote:
> A) Convert the matrix into a mathematically correct one, where it is needed,
> e.g. in case it will be multiplied by another matrix.
> B) Change core to use the mathematically correct matrix.
> C) Other idea?
>
>
Hi all,
the matrix, which is product by TRGetBaseGeometry and which is available
as property "Transformation" in macros, is mathematically wrong, because
the shear element has a wrong sign. What to do?
A) Convert the matrix into a mathematically correct one, where it is
needed, e.g. in case
