ConcatenatedTransform.Inverse() method destroys the state of child transformations

[Nipheris]

The bug is related to ConcatenatedTransform.Inverse() method, which has unexpected side effects on child transformations in the list. Because of the absense of deep cloning of child transformations in Clone(), the call of Invert() method on the cloned ConcatenatedTransform object leads to subsequent calls of Invert() on the original child transformations.

To fix this I suggest to reimplement ConcatenatedTransform.Inverse() method to make him create the new ConcatenatedTransform object from the subsequent calls of Inverse() on child transforms (not Invert()).

[FObermaier]

A unit test to prove your point and a patch file would be great.

[Nipheris]

Sure, I will fork the repo a bit later, and will provide fix and testcase.

[Nipheris]

Magnificent!! You fixed this! Thanks a lot!

Time to throw away our nasty workarounds 😀