EDIT: I edited this post because I originally thought this was a cosmetic defect, but it’s more than that - since the relative position of the copied objects changes (In some cases, it may be nearly impossible to recover).
RE-EDITED to simplify the process of recreating the bug.
Just stumbled across an interesting defect - pretty sure it’s been there since layers were introduced, but I just saw it on 6.11 Beta:
It appears that only the third object was copied (because of the offset)…however…it turns out that the other objects were also copied, but because they’re in another layer, they don’t cause the offset. If we move the copied objects away, we reveal the originals:
Objects are only shifted if they’re being copied to the original layer where they’d overlap the original completely. If being duplicated to a new layer, they’re not shifted.
I don’t understand…The problem is that if I copy three objects, the resulting copy’s positions, relative to each other, change. You can’t keep them together even though you’re copying them together. How is that “intended”?
EDIT: Furthermore, you’re telling me that depending on the layer situation, copy now behaves differently - and unintendedly. How is this correct?
Now let’s copy all objects with different layers activated:
With Layer 1 Activated:
With Layer 2 Activated:
With Layer 3 Activated:
Think about what the user is trying to do. The relative position of the objects is only maintained in 1 of 3 scenarios…and as far the offset, it’s different all three times.
I’m guessing the rule is that, if the object being copied overlaps objects in the layer, they’re shifted - if not, not. That logic violates the intent of the user…who just wants to copy three objects together and most likely wants to preserve their positions relative to each other.
Suppose I’m a smart enough user to understand this subtlety…and I want to copy all three relative to each other…what are the steps that I need to take to do that, if they’re on different layers (which I would do for some logical reason that shouldn’t be impacted by this)? Think about what we’re putting the user through with this.