Bug 54125 - angle's ratio modification will not remain when saved and reopened file
Summary: angle's ratio modification will not remain when saved and reopened file
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
3.6.0.4 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-27 15:07 UTC by arh1001
Modified: 2015-02-11 19:57 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
A sample of the drawing; when reopened the file, only the rectangules saved as libreoffice draw will not keep their original modified shape, which can be seen in the GDI Metafile copy. (16.87 KB, application/vnd.oasis.opendocument.graphics)
2012-08-27 15:07 UTC, arh1001
Details

Note You need to log in before you can comment on or make changes to this bug.
Description arh1001 2012-08-27 15:07:21 UTC
Created attachment 66179 [details]
A sample of the drawing; when reopened the file, only the rectangules saved as libreoffice draw will not keep their original modified shape, which can be seen in the GDI Metafile copy.

After creating an organization chart and having modified the ratio angles of rectangules to soften the edges, they would recover their original shape (before ratio modification)when saved and reopened the file. 
The very same occurs when the graphs are copied and pasted onto another libreoffice document, except when pasted as gdi metafile or bitmap.
See example attached.
Comment 1 Hashem Masoud 2012-10-25 14:01:31 UTC
Is this being handled in bug 43209? If yes then please mark as duplicate.

Myself I can confirm that flow chart boxes cannot be rounded. But you can use rounded rectangles instead (from basic shapes).
Comment 2 QA Administrators 2015-01-05 17:52:18 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team
Comment 3 Buovjaga 2015-01-20 16:00:00 UTC
Bug never confirmed by QA.

To original reporter: do you still have a problem with this?
Comment 4 QA Administrators 2015-02-11 19:57:50 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 

Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Message generated on: 2015-02-11