Created attachment 58760 [details] odg with hatched polygon (like map of a building) In the case a DRAW document with small scales contains polygonal hatched areas (german: Polygone mit Schraffur), and this document was saved with LibO 3.4 the objects will be corrupted when opened in LibO 3.5 The given example will IMHO reproduce the effects. Test conditions of the following benchmark data: OS: Windows Xp Pro SP3 CPU: Intel Core i5-2410M 2.30 GHz RAM: 3 GB Effects reproduced with LibO 3.5.0 Release, 3.5.1 Release, LOdev3.5.2RC-nightlyBuild20120319 on WindowsXpSP3 AND LibO 3.5.0 Release on Windows7Pro-64bit Attachments: example_plan_hatched_polygons_LO3.4.5.odg: Source saved in LibO 3.4.5 Screenshots: 01-FILESAVE-in_LibO3.4.5-example_plan_hatched_polygons_LO3.4.5.jpg 02-FILEOPEN-in-LibO3.5.1.2-example_plan_hatched_polygons_LO3.4.5.jpg 03-FILEOPEN-in-LOdev3.5.2NB20120319-example_plan_hatched_polygons_LO3.4.5.jpg
Created attachment 58761 [details] situation when FILESAVE in 3.4.5
Created attachment 58762 [details] situation after FILEOPEN in 3.5.1.2
Created attachment 58763 [details] situation after FILEOPEN in nightly build LOdev3.5.2 20120319
Confirmed with LibreOffice 3.5.0 and the attached Testfile. I think, the same Bug, I have with other Libre Draw Files. Generate with 3.4.3 the File is fine and after FILESAVE and FILEOPEN in 3.5.0 the positions of many objects are changed. I can restore this Bug, If I export a Drawing from Inkscape in ODG and open it with LibreOffice 3.5.0: After FILEOPEN the drawing is fine, after FILESAVE and FILEOPEN it is distroyed.
Hi, There are other problems of compatibility between LibO 3.4 and LibO 3.5 Cf fdo#47699 FILEOPEN: object saved with 3.4 opens bad with 3.5 https://bugs.freedesktop.org/show_bug.cgi?id=47699
Issue #47406 https://bugs.freedesktop.org/show_bug.cgi?id=47406 Almost all graphics that have internal circuits are not rending correctly deals with same kind of problem
I have tried the document with LO3.5.2rc2 and can see the error no longer. So I think too, that it is the same reason as Issue #47406. *** This bug has been marked as a duplicate of bug 47406 ***