Just plain usage of log10 are gives not best result in case of rounding and when working near little values (0<all<1)
That's a fair point. I made the changes to be able to handle negative values and refactored not to use strings to gauge magnitude and to allow for unit tests.
Without a detailed review and test cases I can't be sure but I think you would only need to submit a patch/pull request (with tests!) for my _max_min() method, I'd be happy to include it.
Thanks, i'll try your implementation, and probable port to your one that logic.
Have not read yet your code, but:
do you assume always that min and max are "auto"?
do you plan to support override of some of boundary (min/max) and auto-calculate other half?
=== and btw:
Anyone still support single openpyxl instance?
I'm prefer to just "easy_install openpyxl" in bootstrap script, rather than installing via checkout of some branch from somewhere...
I have some working code where you can actively set axes' min and max but it's a bit hit and miss (the values are set and readable but not always reflected in the resultant charts). Although I have changed how things work I have tried to keep behaviour the same for existing users, so the default is auto-calculation. It's probably a bit over the top at the moment to ensure this.
I can add a download of my current status so this will at least work with easy_install either with a local download or by finding links. I think that's the best we can do at the moment without making an official fork of the project.
@datacompboy my fix is in the 1.8 branch and includes support for overriding auto axis calculation for charts. Release should be sometime soon.