Ah -- for some reason the benefit is immeasurable until about 1M
points. I was using fewer points because you can't even get a baseline
measurement with that many -- it exceeds the path length limit in Agg.
I see now why it's superior to the clipping I wrote -- it does a binary
search to find
Michael Droettboom wrote:
> According to svn blame, which only gives the most recent version a line
> was edited, not the first time a line appeared, obviously -- subslice
> support was added in r7100, and clipping was fixed in r6847. So,
> apparently at the time subslice was added the clipping
According to svn blame, which only gives the most recent version a line
was edited, not the first time a line appeared, obviously -- subslice
support was added in r7100, and clipping was fixed in r6847. So,
apparently at the time subslice was added the clipping was already
there. So, if you w
Michael Droettboom wrote:
> We recently saw some breakage with our PyRAF plotting tool (which uses
> matplotlib as a "dumb" rendering backend) and matplotlib 0.99. It stops
> inside the subslice support that was added to Line2D, since subslicing
> requires that the Line2D object have an "axes"
We recently saw some breakage with our PyRAF plotting tool (which uses
matplotlib as a "dumb" rendering backend) and matplotlib 0.99. It stops
inside the subslice support that was added to Line2D, since subslicing
requires that the Line2D object have an "axes" assigned to it. Since
PyRAF does
