Bug#231730: floating-point value for max_val option is broken

[Bill Allombert]

On Sun, Mar 26, 2006 at 08:12:15PM +0300, Niko Tyni wrote:
> In your other mail, you state:
> 
> > It seems the option "integer_ticks_only" does not work:
> 
> but for me it does. For example, your example script with data
> consisting only of integers '0' and '1', the default behaviour without
> 'integer_ticks_only' is to have a scale of .2 units per tick (with a
> precision of 3), while with 'integer_ticks_only', there are only the
> ticks for '0' and '1'. Could you be more specific, please?

Hello Niko,

Thanks for fixing the colors and looking at this problem!

Please try this script to see why I said integer_ticks_only
did not work:

--------
#! /usr/bin/perl -w

use Chart::LinesPoints;
@data=([2000..2200], [0..200]);
$obj=Chart::LinesPoints->new (600,400);
$obj->set ('max_y_ticks' => 6);
$obj->set ('min_y_ticks' => 2);
$obj->set ('integer_ticks_only' => 1);
$obj->png ("foo.png",\@data);
--------

You get 200 Y ticks (which are unreadable) disregarding the max_y_ticks of
6. If you remove integer_ticks_only, you get just 3 ticks.

The manpage says:
       'integer_ticks_only'
           Specifies how to draw the x- and y-ticks: as floating point
           ('false', '0') or as integer numbers ('true', 1). Default: 'false'

which does not warrant this behaviour.

Cheers,
Bill.