 |
This seems to happen after a rotation has been applied to the entity in question. I'll add some repro steps. |
|
|
The problem arises due to the rather nontrivial way the Transformable scene nodes are applying their assigned scale/rotate/translate values in a pattern of setTransform/transformChanged/evaluateTransform/revertTransform/freezeTransform/whateverTransform. The pattern is repeated across many classes, but there are slight differences every time it's applied. With regards to this problem It appears that GenericEntityNode::freezeTransform() is overriding the base method without ever calling it. When freezeTransform() is invoked by the transformation visitors, the Transformable::_rotation member is not reset and it's applied in every new transformation round. All the other node types don't override the method, so the rotation is properly cleared to its identity value. |
 |
I barely understood most of that, so does the above explain why it only happens after it been open for a while and not after a fresh run of DR. |
|
|
nice one Greebo. |
- Anonymous
