On Sun, Jul 27, 2008 at 4:57 PM, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> My inclination is to avoid diamond inheritance in this case by > moving the wx base class to wxagg. Let me know and I will > implement it. My weak preference would be to do this as a mixin factorint out the renderer from the GUI stuff. If this is only marginally harder, it makes it easier down the road if someone wants to mixin a different renderer from agg, or if the wx renderer ever improces sufficiently to make it usable. But if this seems like a lot more work, I am not averse to simply deprecating the wx renderer, though factoring everything to make mixing in a different renderer later will still be useful. In the end, whatever you decide will be fine. > There is one more outstanding change to wx before I can stop > subclassing the WxAgg canvas in my own applications, which is > that draw is being called too often. Putting a print statement in > WxAgg draw and _onPaint I get the following: OK, now that we have missed the debian freeze, the pressure to get something out sooner is lessened, do we'll just work on getting it right. JDH ------------------------------------------------------------------------- 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
