tiled clones original moves when copied/pasted with its array

[Brynn]

Hello,
Originally reported on InkscapeForum: http://www.inkscapeforum.com/viewtopic.php?f=5&t=13519

When you make a tiled clones array, and copy the entire array plus the original, then paste, the original object is no longer associated with the 1st clone. I'll attach a test file.

In layer "Layer1 - black", you can see the original array of black star/blobs on the left, with the original object still behind the 1st clone. When the array and the original is copied and pasted, you can see on the right, that the original object ends up a short distance below the array. Layer 1 exists in a custom default doc which has had its orientation changed from default portrait to landscape. I'm told this adds a transform attribute, that is either added inappropriately, or causes objects on canvas to behave inappropriately. That's my current understanding, and it may not be correct, but it's what prompts me to think this may be a bug, and may be related to the transform attribute.

In layer "Layer2 - blue", you can see the appropriate behavior. By creating the 2nd layer, I've avoided the well-known transform attribute-related bug(s) caused by the landscape orientation of the custom default doc.

It seems to me this may be related to bug #168651: https://bugs.launchpad.net/bugs/168651 But I will leave it for the experts to decided the particulars :-)

Here comes the file, and thanks for listening :-)

Brynn

[Brynn (brynn4inks-deactivatedaccount)]

Oops, I forgot to say this is on Inkscape 0.48.4, and Win7Home, 64-bit. Sorry :-(

The op on InkscapeForum reports Inkscape V0.48, Win 7 Pro 64-bit.

Another member got some different results that aren't clear to me. Link to their reply, which includes an SVG file attachment: http://www.inkscapeforum.com/viewtopic.php?f=5&t=13519&p=52903#p52260 This member did not have trouble in a brand new file. But the problem does happen in a new file for me. I think that's probably because this member's default file does not contain the troublesome transform attribute.

Thanks again :-)
brynn

[su_v (suv-lp)]

Grobe (pRototype) already filed this 2 days ago, with a slightly different sample file. Not surprisingly, the trigger is the 'transform' attribute of the layer.

Linking as duplicate to bug #1152657.