AD2.1.1: Bug in Layer > Arrange > Move Inside

[purplie]

Summary: The object to be clipped unexpectedly moves when using Layer > Arrange > Move Inside (instead of using "Paste Inside", or dragging the object onto the clipping path in the Layers panel).

Application:  Affinity Designer 2.1.1

OS: MacOS 13.5

Reproducible: Yes.

Detail:  Open the attached .afdesign file.  You see an image and a clip path.  The task is to apply the clip path to the image.

Either of the following procedures gives the correct result:

A.  (Works.)  Select "theImage"; then "Cut"; then select "theClip", then "Paste Inside".

B.  (Works.)  In the Layers panel, drag "theImage" onto "theClip".

The correct outcome looks like this:

However, the following procedure gives an incorrect result:

C. (Doesn't work.)  Select "theImage"; then "Layer > Arrange > Move Inside".

As you can see in the screenshot below, "theImage" has moved inside "theClip" according to the Layers panel; but notice that the X/Y coordinates of the image have inexplicably moved, so that it no longer is within the bounds of "theClip".

Additional notes:

1. The manual says that the action of "Arrange > Move Inside" is that it "moves the object inside the object above it on the Layers panel".  That's a typo; it actually moves the object inside the object below it.

2. If you first move the image and clip path outside the layer, then it works as expected.

3. The reason I wish to use method (C) instead of methods (A) or (B) is that it's more suited for scripting with an external macro utility.  

Thanks for your consideration.

bug-7.afdesign

[Return]

Tried this out with the latest beta version 2005 on windows and it worked as intended.
Perhaps it's a mac only issue.
You did mention an attached afdesign file which isn't present for anybody to test out with.

[Return]

But yes, the wording should be altered in the help files.
Select object>arrange>move inside == it will become a child of the first layer below the selected object and be clipped to the boundaries of this layer.

[purplie]

Sorry, here is the missing attachment.  I don't see the bug all the time; there may be something in this particular file triggering it. 

bug-7.afdesign

[Callum]

I have logged this with our developers to be investigated further. I'll let you know once I have an update

[lepr]

It's a known bug from v1.x.

Attached is another simple example in a v1.10.6 document.

Move Inside bug.afdesign

The video shows the outer container (it can be a Layer/Group/object) crucially being transformed after the other objects are put inside it, and then the subsequent 'Move Inside' which involves a miscalculated transform.

 

 

 

 

 

[Hangman]

FWIW, in both instances, the issue appears to be pertinent to the first Layer (Capital 'L') only...

[lepr]

3 hours ago, Hangman said:

FWIW, in both instances, the issue appears to be pertinent to the first Layer (Capital 'L') only...

As I already said, if the container (a Layer in these cases) has been transformed after the objects have been put in it, a subsequent Move Inside will involve a miscalculated transform. My video showed that happening.

Maybe I should have added a superfluous statement that if the container has not been transformed after the objects have been put inside it, a subsequent Move Inside will involve a correctly calculated transform.