Red Hat Bugzilla – Bug 288701
Charting additional Y-Axises use scaling of first Y-Axis
Last modified: 2008-04-04 09:14:40 EDT
Description of problem:
I'm trying chart two properties gas price and miles/gallon, all versus the date.
The two gas prices share the same Y scaling. The third is scaled on the left
side of the chart (correctly). The plotting of the points for the third is way
off the chart (I added a zero entry to show a known point with a line linking).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. See attached gnumeric file
2. See properties for chart: Graph->Chart1->Y-Axis3 (Scale tab)
3. Data is in Graph->Chart1->PlotXY1->Mi/Gal (Data tab)
The zero point is plotted (orange triangle), following points are off the top of
All data points plotted
Created attachment 194151 [details]
Gnumeric file of gas prices and mi/gal plotted versus date
If I change the maximum scaling of the Y-Axis1 from 4 to 40, the scaling for the
other two Y-Axises also changes and Y-Axis3 data points show up.
Sorry for the long silence.
Rawhide now has gnumeric 1.8.1, can you please check if this bug still happens
with gnumeric-1.8.1 ?
Yes, 1.8.1 still does it. In the file attached in Comment #1, it requires that
the values in column G be divided by 10 before they show up in the graph. The
values are being plotted by the first scale rather than their own.
(In reply to comment #4)
> Yes, 1.8.1 still does it. In the file attached in Comment #1, it requires that
> the values in column G be divided by 10 before they show up in the graph. The
> values are being plotted by the first scale rather than their own.
Thanks for testing, I'm afraid I'm not familiar enough with gnumeric's code to
fix this easily, and I expect someone who is familiar with the code to have an
easy time at fixing this. So can you please file this bug upstream:
And then report the upstream ticket number here? Many thanks!
I've filed this myself upstream now, feel free to add yourself to the CC:
FYI: Upstream says this is not a bug, but you are using the charting component
the wrong way causing your issues, they've attached a corrected file which does
behave as you want, see: