© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Two references to what seems to be a known problem:
A) detailed earlier comment by Pjrm in bug #168651 about page resize:
<quote>
A second question is how Fit canvas to selection should implement its
translation step, whether adding a transform attribute to the group as it
does now or whether to go more deeply. If the latter, then how deeply? If
fully deeply, then beware of issues with objects in a group being cloned
(especially if that group has a rotation transformation): need to be
careful about how to adjust the clone's transform.
</quote>
<https:/
B) related posting in inkscape-devel:
From: bulia byak
Subject: "clone behaviour"
Date: 2009-07-03
<quote>
> -transform management: create an object A, create a clone A' of it, put A'
> in a group G. Now select A and G and rotate them. A' is rotated twice!!!
I have spent quite a time coding around issues like this and ensuring
that clones transform intuitively, using compensations. However my
calculations are limited to the simple case of naked clones. If you
put a clone in a group and transform the group, or use clone of clone
chains, this will still behave wrong. But it's not some unfixable
problem. The code for compensations is there, we just need to make
this code smarter and make it look farther around the clone to figure
out the correct compensating transformation. Maybe it was just me, but
I found this too difficult, so I limited myself to the simple case -
someone more mathematically gifted can probably crack it easily. Give
it a try.
</quote>
<http://
I haven't yet found an earlier report of this issue (besides the possibly related one about the clone-tiler) but since it has been unsolved for some time I expect there must be other reports describing unexpected behavior of clones or their original objects in transformed groups. Anyone?