Thanks for the report. I can see the problem - the default
minimum range has been set to a very small value, but when a
zero range is encountered (as in the case where there is
only a single data value), the computation that expands this
range to the minimum allowed is losing precision and ending
up as zero anyway. Restoring the default minimum range to
0.000000001 will work for the most common data values (so
I'll do that for the next release), but would still be
subject to the same problem for very large data values.
I'm not sure what is the best solution. Perhaps the minimum
axis range needs to be set as a percentage of the data value...
Regards,
Dave Gilbert
JFreeChart Project Leader
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=112975
Thanks for the report. I can see the problem - the default
minimum range has been set to a very small value, but when a
zero range is encountered (as in the case where there is
only a single data value), the computation that expands this
range to the minimum allowed is losing precision and ending
up as zero anyway. Restoring the default minimum range to
0.000000001 will work for the most common data values (so
I'll do that for the next release), but would still be
subject to the same problem for very large data values.
I'm not sure what is the best solution. Perhaps the minimum
axis range needs to be set as a percentage of the data value...
Regards,
Dave Gilbert
JFreeChart Project Leader
Logged In: YES
user_id=960531
sun.dc.pr.PRException: endPath: bad path.
This is due to a known bug in the Sun AWT classes and is
reported on http://java.sun.com/ as bug 4485298.
chart.setAntiAlias(false);
seems to fix the problem