(oops, I meant to send that to the matplotlib list)
Hi,
I was looking at the transform code recently..
On Thu, July 19, 2007 7:31 pm, John Hunter wrote:
> The potential cost is not in the 3x3 vs 4x4, but in the extra row of
> junk data you would store in the data matrix, which is N extra values
Somehow I accidentally deleted a line in a part I thought I hadn't touched.
It's a two line change, so I'll just tell you what to change:
Find the line:
set_clipbox_rasterizer(gc.cliprect);
in src/_backend_agg.cpp in the draw_lines function. (around line 1500)
Right after it, add the following
That seems to have to do with the line culling agg patch I sent. I never
thought to check with polar plots. I'll look into it.
Allan
On Thu, July 19, 2007 12:17 pm, Paul Kienzle wrote:
> The polar demo in examples/polar_demo.py no longer displays the spiral
> and axes. It worked a couple of wee
John (and others),
I've made a quick change to the svg backend to cull the data, see attached
patch. I haven't tested it extensively, but it seems OK. It culls both
lines and polygons out of svg output.
About making it general across backends: I've looked a bit at how things
get rendered, and her
On Mon, July 9, 2007 10:57 am, John Hunter wrote:
> I wonder if you cached some of the interval tests whether you might
> see some additional speedups. Eg, something like
>
You could do this, but I don't think you would even notice the difference.
Really, my impression is that the only thing
Hi,
First, I noticed a bug in the version I sent before. I've attached a new
version in patch form, to be applied from the base directory of a normal
0.90.1 installation with 'patch -p1 John,
>
>
> Have you considered Allan's version of _backend_agg.cpp (message date
> was 06/27)? I just tried i
