Mike, A bug was recently pointed out: axhline, axvline, axhspan, axvspan mess up the ax.dataLim. I committed a quick fix for axhline and axvline, but I don't think that what I did is a good solution, so before doing anything for axhspan and axvspan I want to arrive at a better strategy.
What is needed is a clean way to specify that only the x or the y part of ax.dataLim be updated when a line or patch (or potentially anything else) is added. This is specifically for the case, as in *line, where one axis is in data coordinates and the other is in normalized coordinates--we don't want the latter to have any effect on the dataLim. This could be done in python in any of a variety of ways, but I suspect that to be most consistent with the way the transforms code is now written, relying on update_path_extends from _path.cpp, it might make sense to append two boolean arguments to that cpp function, "update_x" and "update_y", and use kwargs in Bbox.update_from_path and siblings to set these, with default values of True. What do you think? If you agree to the _path.cpp change strategy, do you prefer to do that yourself, or would you rather that I try it first? Any suggestions and/or contributions are welcome. Thanks. Eric ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel