Problem summary
A Child Locator adds the Parent Object's transform to a LocatorList's transform fields upon creation
Customer reported version
Mari 6.0v2
Customer reported platform
Multiple
Steps to reproduce
- Open any project that has no Object transform applied, such as the Material Design Example Project
- Create a Projection node
- In the Node Properties, add any image, and set Clip to Both
- Using the Transform Selected Objects tool, transform the materialGeo Object in any way
- In the Projection section of the Projection node, click the + button to create and pick a Child Locator
Expected behaviour
In the Node Properties,
Projector Translation/Rotation/Scale remain the same, and the projected image also doesn't move.
Actual behaviour
The Object's transform settings are added to
Projector Translation/Rotation/Scale, and the projected image moves accordingly.
If the
+ button is clicked again, the Object's transform settings are added again, moving the projected image further away from its original position.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Mari 6.0v2 - Windows 10 - CentOS 7
Mari 5.0v3 - Windows 10 - CentOS 7 - Regression
Unable to reproduce bug in:
Mari 5.0v2
Earliest version tested
Mari 5.0v2 - This issue doesn't appear in this version and has regressed