Bug 132430 - Draw: Copy & paste a grouped object doesn't preserve the layer of single components
Summary: Draw: Copy & paste a grouped object doesn't preserve the layer of single comp...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Layers
  Show dependency treegraph
 
Reported: 2020-04-26 10:52 UTC by Giorgio Croci Candiani
Modified: 2022-05-06 08:16 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example document showing bug (74.70 KB, application/vnd.oasis.opendocument.graphics)
2020-05-12 08:35 UTC, Giorgio Croci Candiani
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Giorgio Croci Candiani 2020-04-26 10:52:07 UTC
Description:
When copying a grouped object containing parts on different layers, pasting puts all parts on the target layer rather than preserving the original ones

Steps to Reproduce:
1.Draw several object on different layers.
2.Group these objects (Ctrl-Shift-G)
3.Select the grouped object and copy it with Ctrl-C
4.Paste the obj with Ctrl-V to any layer "X"
5.Ungroup the obj group (Ctrl-Alt-Shift-G)

Actual Results:
All the copied sub-objects are on layer "X"

Expected Results:
All the copied sub-objects should have retained their original layer


Reproducible: Always


User Profile Reset: No



Additional Info:
Versione: 6.3.5.2 (x64)
Build ID: dd0751754f11728f69b42ee2af66670068624673
Thread CPU: 4; SO: Windows 10.0; Resa interfaccia: GL; VCL: win; 
Versione locale: it-IT (it_IT); Lingua interfaccia: it-IT
Calc: threaded
Comment 1 Xisco Faulí 2020-05-11 07:53:26 UTC Comment hidden (obsolete)
Comment 2 Giorgio Croci Candiani 2020-05-12 08:35:03 UTC
Created attachment 160714 [details]
Example document showing bug
Comment 3 Timur 2020-07-07 14:28:23 UTC
Looks as reported in OO 3.3 and master 7.1+.
Comment 4 Giorgio Croci Candiani 2022-05-06 08:16:17 UTC
Two years and the bug is still marked as "New", despite being a pretty basic flaw.  Not impressing at all.