Michael Droettboom wrote: > John Hunter wrote: >> On Wed, Oct 8, 2008 at 11:37 AM, Michael Droettboom <[EMAIL PROTECTED]> >> wrote: >> >> >>> I figured this out. When this happens, a RuntimeError("Agg rendering >>> complexity exceeded") is thrown. >>> >> Do you think it is a good idea to put a little helper note in the >> exception along the lines of >> >> throw "Agg rendering complexity exceeded; you may want to increase >> the cell_block_size in agg_rasterizer_cells_aa.h" >> >> in case someone gets this exception two years from now and none of us >> can remember this brilliant fix :-) >> > We can suggest that, or suggest that the size of the data is too large > (which is easier for most users to fix, I would suspect). What about: > > "Agg rendering complexity exceeded. Consider downsampling or decimating > your data." > > along with a comment (not thrown), saying > > /* If this is thrown too often, increase cell_block_limit. */ > > Mike >
Mike, Thanks for doing this--it has already helped me in my testing of the gappy-path simplification support, which I have now committed. As you suggested earlier, I included in path.py a check for a compatible codes array. The agg limit still can be a problem. It looks like chunking could be added easily by making the backend_agg draw_path a python method calling the renderer method; if the path length exceeds some threshold, then subpaths would be generated and passed to the renderer method. 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