hi guys, thanks for a great lib. I've noticed a bug or two so thought i'd post.

in 2.0.12, in pDraw.class

I believe this says:

and throws a notice (or warning?) when using axisalpha but not gridalpha

working:


- - 8< - - snip - -

I wasn't sure where to suggest this so:
sometimes it is required to produce a bar chart that shows deviation from a custom value, i.e. bars wrapping not around zero but arbitrary value. I struggled to produce this using ordinary methods (yes you can but on close inspection the bars are wrong), so here's a proposed code change:



in pDraw::drawBarChart()



- - 8< - - snip - -

(finally, as a suggestion, environments like Zend assign .class files to Java instead of PHP. This breaks code completion and other project functionality.
Consider .class.php)


hope this works :]

Fixed the issue with the AxisAlpha switch.

I'll add the option to modify the Y wrapping value for the bar charts based on a fixed treshold or another data serie.

Regarding the class extension, I've already get this feedback once. The issue is that it wouldn't be fair to rename the classes for all the users that have started to code with the 2.0, this would require that they modify all the class inclusions from their scripts. Maybe we can place a poll for this?

Kind regards,
JD.

This is more of a technical-design question. I do believe a user would be happy with a single point of inclusion for the whole library in their init scripts, such as

.. that then includes all pChart classes in valid order. The CPU+disk cost of this is minimal. But the outcome is you have a convenient proxy that works fine should you decide to make more drastic changes later.

I am new to pChart2 (but not to pChart) as I guess many other users are. I found it a bit puzzling that I have to include pDraw, pImage, and pPie separately (even though I can see how this makes sense). My theory, seeing that pChart2 is fresh, is that some of the early changes will be seen as investment more than hassle.