On Fri, Mar 12, 2010 at 12:15 PM, Eric Firing <efir...@hawaii.edu> wrote:
> This example is mostly obsolete--the clipping procedure is built-in. (The > value added by the example is the change in marker style.) Right, which is what I was trying to get at in the following: While this may not solve your case, because it looks like you may be exceeding the rendering complexity with data in the viewport, the design pattern may help inspire to you to write a custom class to handle adaptively decimating your data so you can still see a sketch of your data when panned out, but nonethless get the full detail when zoomed in. What I was trying to point out is you can hook into the event handling / callback mechanism to do *custom* level of detail clipping based on viewport or some other feature if the default simplification is not adequate. Along these lines Ivan, you may want to take a look at the event handling tutorial http://matplotlib.sourceforge.net/users/event_handling.html Perhaps we should wework the example to do something more useful that is not already handled better by path simplification. JDH ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
