Take a Draw document.
Enter a drawing object in the middle of the page, for example a rectangle or a textbox.
Rotate the object, for example 30°.
Save the document.
Reload the document.
Notice, the rotated object has its corner at position 0|0.
I see this bug in a self-compiled LibO3.5 on WinXP. So please try it with an actual build, to verify that it is nothing special for my build. My build is made from 5ad4d151dac1eb887d92200330e31af269d8d1fd
Additional comment: The saved file has the correct positions, so the error happens while loading.
The bug is not in my previous build of LibO3.5. I don't know the commit id, but it was before 2011-08-30.
[Reproducible] with parallel installation of MinGW Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: 308b7a2-e916bf9-9c6ea62-e1a2fb3)] (daily/MinGW_cross-compilation 2011-10-18_22.56.49)"
Not reproducible with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: d3d1481-3f8994a-2ba0a9f)]" (110909). Only latest Master versions or only MinGW affected?
It's indeed a FILEOPEN problem, pls. see my attached sample created with LibO 3.4.3. Opening it with an affected Master Version shows all objects at the top left slide corner. Saving document with Master 3.5. will destroy it, opening it again with 3.4.3 will also show all objects at top left corner.
Created attachment 52775 [details]
See Comment 2!
Created attachment 52776 [details]
Writer sample document
Not only DRAW is affected, I see the same problem with rotated DRAW objects in WRITER, please compare view in 3.4 and latest Master.
Raked, I wonder if it is related to your work on shapes. Could you please have a look?
It guess that it is related to the bug 41888.
AFAICS it is not. This bug completely avoids pptx paths.
it adds unwanted translation to odf output:
- <draw:custom-shape draw:style-name="gr1" draw:text-style-name="P1" draw:layer="layout" svg:width="6.604cm" svg:height="6.604cm" svg:x="8.128cm" svg:y="6.35cm">
+ <draw:custom-shape draw:style-name="gr1" draw:text-style-name="P1" draw:layer="layout" svg:width="6.604cm" svg:height="6.604cm" draw:transform="rotate (-0.516442925665122) translate (10.189cm 5.15cm)">
will try to look at it
the translation is OK, because it also removes svg:[xy], looks like odf import doesn't import correctly the transformation
Why is mark as blocker?.
Dataloss, unusable function, reproducible by more users, broken functionality is regression against the last released version, affect most users.
fortunately it wasn't loosing data. just the import was broken.
the problem is now fixed in master
I can NOT confirm a fix with Server installation of MSVC Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: a653e50-1f92ab1-3bd0388]" Win-x86@6 - 111128)
the fix was committed in master on Nov 28th
Author: Radek Doulik <email@example.com>
Date: Mon Nov 28 18:24:11 2011 +0100
I am closing the bug, please reopen if it doesn't work with newer builds.
*** Bug 41808 has been marked as a duplicate of this bug. ***
Sorry, but this bug seems still alive in LibreOffice 3.5 beta 0:
Reopened because bug is still REPRODUCIBLE following Regina Henschels descriptions, using
LibreOffice 3.5.0 [beta 0]
German UI installed
running on MacOS X 10.6.8 German
Could someone else please test Windows and/or Linux?
Sorry again: the bug is really present in LibreOffice 3.5 beta 0, as I wrote, but it is fixed on master -- testet with two of the newest Master builds.
So I hope this bug will be fixed in 3.5 beta 1 or 2, too.
May I propose to leave the Status set to 'REOPENED' until we are sure (by simple end-user testing) that the fix really made it into beta 1 or 2?
For me it is fixed. I'm on WinXP using LOdev 3.5.0
Also WFM with Parallel Dev-Installation of "LibreOffice 3.5.0 Beta1 - WIN7 Home Premium (64bit) German UI [Build-ID: 7362ca8-b5a8e65-af86909-d471f98-61464c4] Windows_Release_Configuration 11-Dec-2011 06:51". So closing again.
Fix confirmed with beta 1 on MacOS X 10.6.8:
LOdev 3.5.0 [should be: LibreOffice 3.5.0 beta 1; on MacOS, the file name of
the beta 1 build is 'LOdev']
Sorry for the confusion my report may have caused! In beta 0, the bug was still present, it has been fixed in beta 1. So everything is good now ...
*** Bug 43287 has been marked as a duplicate of this bug. ***
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.