On 10/19/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> A while back I put in quite a bit of effort into enabling draw_markers in the
> postscript backend. This is an efficient RendererPS function both in terms of
> speed and file size, but it seems to not be used any more in favor of the
> less eff
On 10/19/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> I don't remember how to find the answer. It looks like scatter() creates
> polygons, while plot() uses draw_markers:
I see -- scatter uses collections, and the defaut Renderer implements
PolygonCollection drawing through draw_polygon. This is
On Friday 19 October 2007 03:57:31 am Manuel Metz wrote:
> Now that alpha works with screen output, I recognized a problem with the
> eps output. This is my little test script:
>
> import pylab
>
> x = pylab.npy.arange(0,10)
> pylab.scatter(x,x, s=50, alpha=0.5)
> pylab.scatter(x,x+0.5, facecolor='
Darren Dale wrote:
> On Friday 19 October 2007 10:20:43 am John Hunter wrote:
>> On 10/19/07, Darren Dale <[EMAIL PROTECTED]> wrote:
>>> I don't remember how to find the answer. It looks like scatter() creates
>>> polygons, while plot() uses draw_markers:
>> I see -- scatter uses collections, and
On Friday 19 October 2007 10:20:43 am John Hunter wrote:
> On 10/19/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> > I don't remember how to find the answer. It looks like scatter() creates
> > polygons, while plot() uses draw_markers:
>
> I see -- scatter uses collections, and the defaut Renderer im
On Friday 19 October 2007 05:23:38 pm Darren Dale wrote:
> I'm having some trouble updating a plot window without calling plot. I
> would like to do something like:
>
> ax = axes()
> lines, = plot([1,2,3], [1,2,3])
> lines.set_ydata([4,5,6])
> ax.autoscale_view()
> ax.draw()
>
> The line does get u
I'm having some trouble updating a plot window without calling plot. I would
like to do something like:
ax = axes()
lines, = plot([1,2,3], [1,2,3])
lines.set_ydata([4,5,6])
ax.autoscale_view()
ax.draw()
The line does get updated, but the axes limits are not updated. I've looked
into the Axes.pl
On Friday 19 October 2007 10:55:24 am John Hunter wrote:
> On 10/19/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> > I removed a gsave/grestore pair surrounding RendererPS._draw_ps in
> > svn-3967. It looks like this fixed the problem (graphics state was being
> > lost). I checked contour_demo.py for
On 10/19/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> I removed a gsave/grestore pair surrounding RendererPS._draw_ps in svn-3967.
> It looks like this fixed the problem (graphics state was being lost). I
> checked contour_demo.py for any unintended side-effects, and didn't find any,
> but please
A while back I put in quite a bit of effort into enabling draw_markers in the
postscript backend. This is an efficient RendererPS function both in terms of
speed and file size, but it seems to not be used any more in favor of the
less efficient draw_polygon. Does anyone know why?
Darren
--
There is a minor bug in line 852 in patches.py
verbose.report('patches.Ellipse renderer ...
This has to be
mpl.verbose.report('patches.Ellipse renderer ...
Manuel
-
This SF.net email is sponsored by: Spl
On Friday 19 October 2007 09:21:45 am John Hunter wrote:
> On 10/19/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> > A while back I put in quite a bit of effort into enabling draw_markers in
> > the postscript backend. This is an efficient RendererPS function both in
> > terms of speed and file size,
12 matches
Mail list logo
