After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676339 - object movement when cycled through ODF
object movement when cycled through ODF
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: import/export OOo / OASIS
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Andreas J. Guelzow
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2012-05-18 19:05 UTC by Andreas J. Guelzow
Modified: 2012-05-19 05:36 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
sample xls file (13.50 KB, application/vnd.ms-excel)
2012-05-18 19:05 UTC, Andreas J. Guelzow 		Details

Description Andreas J. Guelzow 2012-05-18 19:05:08 UTC 
Created attachment 214396 [details]
sample xls file

open the attached xls file
save as ODF file
open both files and compare: The red line has moved and enlarged in size.
Comment 1 Andreas J. Guelzow 2012-05-18 19:12:07 UTC 
Note that when the ODF file is opened using LibreOffice, there line is (more or less) in the correct position. The ODF code says:

<table:table-cell>
<draw:line draw:style-name="so-g-l-0x2fcac70" table:end-x="9.98pt" table:end-y="5.06pt" svg:x1="272.67pt" svg:y1="210.60pt" svg:x2="345.98pt" svg:y2="211.86pt" table:end-cell-address="$'Sheet1'.H18"/>
</table:table-cell>

which looks correct

So this is probably an issue with opening the file. Recently code was added to ensure correct placement and size for sheet objects that were included in table:shapes. I suspect that may have affected this situation.
Comment 2 Andreas J. Guelzow 2012-05-19 05:03:36 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 3 Andreas J. Guelzow 2012-05-19 05:36:54 UTC 
But this "fix" caused bug #676355.