Re: Re (tilly) 1: GD::Graph Issues

YIKES! I was planning on using multiple axes in the near future. That is a bad thing for me. What were the 'serious bugs' you found? Would you mind sharing the patch so I can locally patch my module since you can't contact the module author? Thanks!

perl -e 'print reverse qw/o b n a e s/;'

Comment on Re: Re (tilly) 1: GD::Graph Issues

Replies are listed 'Best First'.
Re (tilly) 3: GD::Graph Issues by tilly (Archbishop) on Jan 11, 2002 at 21:51 UTC
The bug issue was that the two_axes option would, if you don't choose data ranges that are extremely "nice" relative to each other, dynamically make very bad choices and insert a huge number of ticks. My change makes it dynamically choose a much smarter range in parallel. The patch that I am posting here is to GD/Graph/axestype.pm. It improves this functionality, but not does not include corresponding documentation patches. (Those should be made in GD/Graph.pm.) It also enhances the y_tick_number option to allow it to take an anonymous array of numbers - it chooses the number of ticks that gives the best fit. The idea for this is based on the existing (undocumented) 'auto' option which corresponds to a range of 3 to 6 ticks. Allowing this results in massively better choices of ranges! (Try it, you will see.) You may wish to change the default value of y_tick_number accordingly. Read more... (15 kB)	[reply] [d/l]

Replies are listed 'Best First'.

Re (tilly) 3: GD::Graph Issues
by tilly (Archbishop) on Jan 11, 2002 at 21:51 UTC

The patch that I am posting here is to GD/Graph/axestype.pm. It improves this functionality, but not does not include corresponding documentation patches. (Those should be made in GD/Graph.pm.) It also enhances the y_tick_number option to allow it to take an anonymous array of numbers - it chooses the number of ticks that gives the best fit. The idea for this is based on the existing (undocumented) 'auto' option which corresponds to a range of 3 to 6 ticks. Allowing this results in massively better choices of ranges! (Try it, you will see.) You may wish to change the default value of y_tick_number accordingly.