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 708649 - Horrible ring plot display
Horrible ring plot display
Status: RESOLVED OBSOLETE
Product: Gnumeric
Classification: Applications
Component: Charting
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jean Bréfort
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-09-23 19:06 UTC by 12spahn46
Modified: 2018-05-22 14:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Terrible looking ring plot (103.09 KB, image/png)
2013-09-23 19:06 UTC, 12spahn46
Details
Exploded OpenOffice Ring Plot (121.29 KB, image/png)
2013-09-27 10:15 UTC, 12spahn46
Details

Description 12spahn46 2013-09-23 19:06:16 UTC
Created attachment 255589 [details]
Terrible looking ring plot

Oh boy, last night I needed to create a ring plot. After entering the corresponding data and creating the chart I thought I was dreaming! Do you really think I can present this horrible locking graph to someone? (See attached screen shot.)

By all means - This should be corrected as soon as possible! Or is there anything preventing you in doing so?

I'm looking forward to your answer.

Bye
Dieter
Comment 1 Jean Bréfort 2013-09-23 20:45:02 UTC
Avoid splitting ring plots, they always look like that.
Comment 2 Andreas J. Guelzow 2013-09-23 23:03:31 UTC
@Dieter, I would be interested in knowing what do you think the plot should look like?
Comment 3 Morten Welinder 2013-09-24 12:15:07 UTC
One could, I think, increase the radius over of the outer pieces by the split
amount, i.e., cut the pieces from a larger circle.
Comment 4 Jean Bréfort 2013-09-24 12:55:05 UTC
Splitting a ring does not change its radius. Of course, we might add a new parameter to change the ring radius before splitting.
Btw, saving to .ods (strict) or .xls and reopening in LO does not give the expected plot.
Comment 5 Andreas J. Guelzow 2013-09-25 06:10:37 UTC
@jean: what do you expoect to see on ods  export and opening by LO? As far as I can tell the Open Document Format has no native way to specify that a ring should be 'split'.
Comment 6 Jean Bréfort 2013-09-25 10:09:24 UTC
Andreas, the series appear in reverse order.
Comment 7 Andreas J. Guelzow 2013-09-26 02:03:39 UTC
It seems that both Gnumeric and LO makes a mistake:

ODF says:
By default, the first series of class ring forms the inner ring and the last series forms the outermost ring. To arrange the rings in opposite order the attribute chart:reverse-direction is set to "true" at the x-axis.

The file uses the default so LO renders the series in incorrect order.

ODF says:
By default, segments are arranged counter clockwise starting at 12 o'clock. To arrange the segments in clockwise order the attribute chart:reverse-direction at the y-axis is set to "true". 

The file uses the default so we should also load the file in the other direction (or write the chart:reverse-direction=true attribute for the y-axis).
Comment 8 12spahn46 2013-09-27 10:15:28 UTC
Created attachment 255911 [details]
Exploded OpenOffice Ring Plot
Comment 9 Andreas J. Guelzow 2013-09-27 20:16:39 UTC
So the OpenOffice ring plot has the same problem: The distance between a piece of "exploded" outer ring and the next inner ring varies from end to end. It is just not as obvious since the (useless) 3d effects hides most information.
Comment 10 Jean Bréfort 2013-09-27 20:43:58 UTC
The radius is the same for all pieces from the same ring. Which looks somewhat logic. Excel does the same thing, and we, as well as OOo and LO, need to have some compatibility with it.
Comment 11 GNOME Infrastructure Team 2018-05-22 14:05:08 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnumeric/issues/238.