Created attachment 129337 [details] exploded donut screenshot The exploded donut (see attached screenshot) uses a wrong calculation for the radius of the exploded slices. As you can see it seems the radius used is the same as the outer radius of the inner ring and the exploded slices are just shifted. My expectation of the result is that the exploded slices use a radius which orresponds to the position where it is drawn so that the exploded slice and the inner slice will never touch (the inner and the exploded slices should be on concentrical circles)
Hello Martin, Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Created attachment 129353 [details] ods showing the bug
Confirmed in - Version: 5.4.0.0.alpha0+ Build ID: 18b3138a7ac4da823e41640bed8a4707029b8fb0 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group - Version: 5.0.0.0.alpha1+ Build ID: 0db96caf0fcce09b87621c11b584a6d81cc7df86 Locale: ca-ES (ca_ES.UTF-8) - LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still repro in Version: 6.3.0.0.alpha0+ (x64) Build ID: de024e572dd7a588f82b84c68daa2051ec6b20e9 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-03-18_01:13:57 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Dear Martin Koller, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still valid for version Version: 7.2.5.1 / LibreOffice Community Build ID: 20(Build:1) CPU threads: 4; OS: Linux 5.16; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-AT (de_AT.UTF-8); UI: en-US Calc: threaded
Created attachment 180509 [details] MS Office rendering of the test case It's not clear exactly what behavior is being requested here. This image shows the MS Office rendering the analogous test case. The basic behavior is the same as that of LO (other than a difference in angular convention, which is distinct from the issue at hand).
"It's not clear exactly what behavior is being requested here." I would expect the exploded rings to have a larger radius so that they are shown concentric to the inner ring to not touch the inner ring. As it is now, it looks ugly
I've submitted a proposed fix for this on branch 104428_patch. Here's the commit comment: tdf#104428 Improve rendering of exploded donut charts This bug shows an exploded donut chart with more than one series. The concern is that the standard pie/donut' explosion' rendering, with the shape of the pieces unchanged but the pieces translated outward, gives unsatisfactory results in the case of a donut with more than one series, where the translated 'exploded' pieces can overlap with the inner ring. This proposed fix renders this case differently, by increasing the radius of the exploded ring but keeping the pieces concentric with the inner ring."
Why was this assigned to me ? What am I supposed to do now ?
I don't know the accepted LO process. I assumed that assigning to the original reporter to verify the fix was the right thing.
Kurt Nordback committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9b558357a3e7a4c908084134d56770809116b4f1 tdf#104428 Improve rendering of exploded donut charts It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Kurt Nordback committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/597bc417192fd9eac58c3cca9527ce5646d9972f tdf#104428 Improve rendering of exploded donut charts It will be available in 7.4.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.