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 413660 - X-axis labeling is not uniform
X-axis labeling is not uniform
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Charting
git master
Other All
: Normal normal
: ---
Assigned To: Emmanuel Pacaud
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2007-03-01 22:59 UTC by Luke Hutchison
Modified: 2007-03-03 02:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A particularly bad case, where intervals switch multiple times (90.46 KB, image/png)
2007-03-01 23:00 UTC, Luke Hutchison
Details

Description Luke Hutchison 2007-03-01 22:59:52 UTC
When resizing a chart, certain widths cause non-uniform labeling of the X axis.  For example, the interval may be 2 (0, 2, 4, ...) and then switch to 3 (8, 10, 13, 16, 19, ...).  The interval should always be consistent.  Probably the max interval over the entire axis should be calculated and used, rather than a local interval based on what is needed to fit the current label.
Comment 1 Luke Hutchison 2007-03-01 23:00:38 UTC
Created attachment 83694 [details]
A particularly bad case, where intervals switch multiple times
Comment 2 Morten Welinder 2007-03-02 01:17:45 UTC
Ugh.  Yeah, that is not pretty.

I doubt the x axis is special here, btw.
Comment 3 Emmanuel Pacaud 2007-03-02 07:56:58 UTC
That's a known bug, and there's nothing easy we can do in order to fix it, as long as we calculate the graph object layout in the graph view.

The current situation is better than what we have a few weeks ago: now what you see in the graph guru should be the same as what you obtain in gnumeric sheet view, whatever the zoom is.
Comment 4 Morten Welinder 2007-03-03 02:01:11 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.