Bug 59142 - EDITING: failing to copy graphic elements (charts)
Summary: EDITING: failing to copy graphic elements (charts)
Status: RESOLVED DUPLICATE of bug 59175
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.0.0.0.beta2
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-01-08 19:04 UTC by Ismael Cedillo
Modified: 2013-01-09 21:15 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
The zipped file attached contains: a spredsheet file with a chart; and three images of a copy-paste process. (245.04 KB, application/zip)
2013-01-08 19:04 UTC, Ismael Cedillo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ismael Cedillo 2013-01-08 19:04:09 UTC
Created attachment 72685 [details]
The zipped file attached contains: a spredsheet file with a chart; and three images of a copy-paste process.

Problem description: Trying to copy a chart element from a spreadsheet to anywhere, generate a bad result (all graphics subcomponents without order and positions)

Steps to reproduce:
1. ....Open a spreadsheet file and create a chart (you can use the file attached) 
2. ....Mark and copy the chart
3. ....Paste into the same spreadsheet or in other documment (impress, writer, etc.)
4. ....The result is a decomposed and disordered graphic (could be a GDI, bitmap or whatever).

Current behavior: The result of copying a chart from a spreadsheet is a decomposed and disordered graphic (could be a GDI, bitmap or whatever).

Expected behavior: when copying a chart from a spreadsheet, the result has to be an image identical to the chart element.

              
Operating System: Ubuntu
Version: 4.0.0.0.beta2
Last worked in: 3.6.4.3 release
Comment 1 Jorendc 2013-01-09 21:15:57 UTC
Thanks for reporting!
I marked this bug as duplicate of bug # 59175;

Normally we mark the older bug reports as duplicate to the first bug report (yours), but in this case we already examined and did some valuable test on the other bug (older). To make sure the developers don't lose/see that valuable information, we mark this bug as duplicate.

Thanks!

*** This bug has been marked as a duplicate of bug 59175 ***