Paul Kienzle wrote: [...] >> Quadmesh has a bug in it that I would love to see squashed. Can you >> look at it, or induce someone else to do so? I tried but couldn't >> figure it out--it is something deep in the use of Agg. It is illustrated >> by examples/quadmesh_demo.py. With masked data (right-hand subplot), >> the masked region is not set to the background but is instead picking up >> odd things. If you don't see it immediately, try reshaping and resizing >> the plot a few times. > > We should be able to track it down. We need to go deep in the code > again anyway to figure out why performance bogs when zooming. We > won't be touching it before the end of summer though. > > - Paul
Good, thank you. This brings up the larger question of the major redesign that is underway, and how to make sure we don't lose the benefit of wonderful speedups like quadmesh. How hard would it be to translate it to use the swig-wrapped version of agg rather than accessing agg directly via the present pycxx _backend_agg.cpp? And how much performance do you think would be lost? Alternatively, is there a better way to put the fast rendering capability in a smaller piece of extension code that can be used in the new framework and that would not rely on pycxx? E.g., a small swiggable chunk? Eric ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
