"move selection to layer above" spreads clones up

[insaner]

r12371

create a new image.
draw a simple rectangle or pretty much any shape i guess..
clone it
create a new layer
select the two objects and "move selection to layer above"
   (ok, this actually will not work, because though you have selected the objects, the top layer is still selected, so you will actually have to select the lower layer and select the two objects and /then/ do selection to layer above)
note that the clone has shifted up..

this is exacerbated when you have multiple clones.. or worse, clones of clones.. where the clones are all moved up into the image, sometimes giving the impression that theyve disappeared

[insaner (insaner)]

might be related to:
Bug #659452 - Ungrouping objects causes translation in clones
Bug #479638 - file gets mangled due to Object->UnGroup Edit
Bug #653574 - Ungrouping moves clones inside nested groups

maybe even:
Bug #168651 - "Tiled Clones" inside transformed groups broken Edit
Bug #802053 - Operation on multiple cloned object gives odd results Edit

[su_v (suv-lp)]

Please attach a sample SVG file to allow further investigation (not reproduced, as expected, with same revision of trunk, default preferences, in a new drawing based on the default template - AFAIK this known problem exposes itself only if the involved layer groups have different transforms e.g. because the user at some point had changed the document page height (or the document page's orientation), and then added the second layer, ore.g. because the new file is based on a custom template which the user created based on a document with such modifications, and didn't remove the 'translate()' transforms from empty layer(s) in the template file.

[insaner (insaner)]

yep, it seems to be exactly that:

"the new file is based on a custom template which the user created based on a document with such modifications"

i guess that makes this a duplicate of one of those bugs

heres what seems to be the best reference:

https://bugs.launchpad.net/inkscape/+bug/479638/comments/7

from Bug #479638 - "file gets mangled due to Object->UnGroup Edit"

a little more prodding with my simple test file and, im not sure, but it seems that at least for this particular case, this could be solved by simply /not/ modifying the transform attribute of the clone during the move.

in my case this was originally transform="translate(0,34.54598)" and when simply "moved to layer above" this was changed to transform="translate(0,-558.8162)". manually changing it back (via the xml editor) to transform="translate(0,34.54598)" fixed the problem.. i dont know how such a code change (ie, modifying the section of code that causes the changes in the transform attribute) would affect other expected behavior, but this would seem to be a pretty trivial fix. is there something i'm not realizing here?

[su_v (suv-lp)]

<off-topic>
On 2013-06-27 24:32 +0100, insaner wrote:
> (ok, this actually will not work, because though you have selected
> the objects, the top layer is still selected, so you will actually
> have to select the lower layer and select the two objects and /then/
> do selection to layer above)

Tracked in
- Bug #168443 “Layer doesn't switch when selecting multiple objects in another layer”
  <https://bugs.launchpad.net/inkscape/+bug/168443>
</off-topic>

[su_v (suv-lp)]

Closing due to lack of feedback (no test case provided to allow to further investigate).

The underlying issue has been reported several times before (see comments), so very likely the report would be a duplicate already,