GNOME Bugzilla – Bug 693895
automatic scaling of Polar Plot sometimes does not work
Last modified: 2018-05-22 13:57:00 UTC
Steps to reproduce: - insert 120 in A1, -75 in A2, 130 in B1, -80 in B2 - select A1:B2 - insert a PolarPlot => the axes are not automatically scaled
For the bug to show up, you need also to insert 140 in C1 and -90 in C2.
Are you trying to work with negative magnitudes? Please attach a sample file and indicate which minimum-maximum range you would expect. Also please explain which axes (plural) you are expecting to be scaled.
Andreas, everything is explained in comments #1 and #2 already. Yes, the exemple contains negative magnitudes (these are latitudes actually). I would expect an automatic scaling in the range [-90,-70].
If comments #1 and 2 would have made sense to me I would not have asked. A polarplot by definition shows a function expressed in polar coordinates. So in my opinion the radial axis should always show positive radii.
Created attachment 236611 [details] sample gnumeric file If I plot a rose as shown in the second plot in the attached file, I would not expect the radial axes to be scaled to [-1,1]. Now in your case I would expect the radial axes to be scaled to [0,90] since this would show allow magnitudes down to -90 to be shown.
In your example, you can use the abs() function. Currently, the radial axes in gnumeric do support negative values, it is just the automatic scaling which does not work in this case.
I believe it is a feature. The default is to have polar coordinates, from 0 to the maximum value. Polar axes do support negative values, but you need to adjust the axis scale accordingly. I'd vote for a wontfix there.
Hi Jean, If the desired default behavior is to set the minimum to 0, why not un-checking the automatic check-box and explicitly setting the minimum to O? That would leave to people the possibility to automatically scale the axis to sensible values.
Not sure it's a good idea. I need to think about that.
-- 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/211.