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 708292 - pbs with the scale of a pseudo 3D axis
pbs with the scale of a pseudo 3D axis
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Charting
git master
Other Linux
: Normal normal
: ---
Assigned To: Jean Bréfort
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2013-09-18 13:54 UTC by Frédéric Parrenin
Modified: 2013-09-21 14:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frédéric Parrenin 2013-09-18 13:54:56 UTC
- open the following file:
https://docs.google.com/file/d/0BzX8dPORePBsMFhUMURkX1REWEk/edit?usp=sharing
=> the pseudo 3D axis is not properly scaled, while automatic scaling is selected
- change the max to 1000000 and the principal ticks to 200000
- copy the chart and paste it to LibreOffice Impress
=> the unmodified chart is copied, the changes have been skipped
- save the file and reopen it
=> the changes to the chart have not been saved correctly
Comment 1 Jean Bréfort 2013-09-18 14:03:58 UTC
I don't see any valid data associated with the pseudo 3D axis, so it's not surprising that automatic scaling does not work.
Comment 2 Frédéric Parrenin 2013-09-18 15:50:59 UTC
There are valid data.
If you change max to 1000000 and major tick to 200000, they appear.
Comment 3 Jean Bréfort 2013-09-18 16:53:20 UTC
The pseudo-3D axis in the "Age" sheet is linked to D15:D115 in the same sheet and all these cells display '#NAME?'
What am I missing?
Comment 4 Frédéric Parrenin 2013-09-19 08:08:14 UTC
You probably need to activate the TSA plugin.
Comment 5 Jean Bréfort 2013-09-19 08:36:45 UTC
OK, I see the issue now. Although the automatic scaling is max=1000000 and major ticks=200000, so I can't change them to these values (what's wrong there?)
Anyway changing max to something else does not persists after copying or reopening the dialog.
Comment 6 Frédéric Parrenin 2013-09-19 12:37:28 UTC
After an update to current git I see the same behavior than yours.
Comment 7 Jean Bréfort 2013-09-19 13:00:49 UTC
At the moment I'm unable to build a simpler case showing the issue, which would be very useful to ease debugging.
Comment 8 Jean Bréfort 2013-09-21 13:15:53 UTC
Found what makes this problematic: the issue seems to appear when the contour plot is not the first plot, and this bug looks ancient. I could build a simple test case. Now, need to understand why this happens.
Comment 9 Jean Bréfort 2013-09-21 14:28:16 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.

We used to remove all axes with types outside of the axes sets of the various plots, so after adding an XY plot, pseudo3d and color axes were destroyed if another plot using these axis types was not already present. I hope that not removing these axes does not break something else. At least, it does not break anything I tested.