Michael Droettboom wrote:
> I've gone ahead and fixed this in the Polygon patch. As you point out,
> if someone wants an open polygon, they can use PathPatch, and Polygon
> was never able to do that before anyway.
>
> Cheers,
> Mike
Hi Mike,
1) I think that there is a bug in the patch: xy is
Hmm... Can't reproduce this here. Maybe it's Python 2.4-specific
(which I don't have).
As a workaround, does replacing line 216 with:
ParseFatalException.__init__(self, pe.pstr, pe.loc, pe.msg,
pe.parserElement)
work?
Mike
John Hunter wrote:
> I'm getting an error with a mathtext string
Not hard, I don't think. The following will give you a FT2Image object
of the expression:
from matplotlib.mathtext import MathTextParser
mathtext_parser = MathTextParser("Bitmap")
ftimage = mathtext_parser.parse(r"$x^i$", 150)
From the FT2Image, you can get an rgba buffer, and the width and th
Thanks. I have fixed 1), and added a "closed" kwarg to fill() and
Polygon.__init__() (which defaults to True to mimic behavior of 0.91 and
earlier). hist() has been updated to call fill() with closed=False.
Cheers,
Mike
Manuel Metz wrote:
> Michael Droettboom wrote:
>> I've gone ahead and fix
Quoting John Hunter:
> Alternatively you can connect to the figure dpi_changed event -- there is
> an example in Axes.cla
Regarding that example, each call to Axes.cla connects a new dpi_changed
callback, but, as far as I can tell, the callback is never disconnected.
Thus, each cla call augments
You're absolutely right that it needs to be fixed.
However, I wonder why the CallbackRegistry doesn't just store the
callbacks in a set (or keys of a dictionary) such that multiple adds of
the exact same function or method to the same signal couldn't occur.
Since there is no external state sto
Michael Droettboom wrote:
> Thanks. I have fixed 1), and added a "closed" kwarg to fill() and
> Polygon.__init__() (which defaults to True to mimic behavior of 0.91 and
> earlier). hist() has been updated to call fill() with closed=False.
>
> Cheers,
> Mike
Great - thanks. So, I committed a p
Olle Engdegård wrote:
> Hi,
>
> Some more thoughts about hist():
>
> A "range" parameter should be added and used in histogram()
Hi Olle,
what do you mean by "range" parameter. What should this parameter
actually do ?
I just committed a patch to the trunk that adds the features as you
a
I've not studied or used the CallbackRegistry, so I've got nothing to add on
that front. However, may I submit the attached work-around for Axes.cla?
Instead of offsetting the title using Affine2D().translate( ... figure.dpi
... ), it uses ScaledTranslation( ... figure.dpi_scale_trans ...). This
Stan West wrote:
> I've not studied or used the CallbackRegistry, so I've got nothing to add on
> that front. However, may I submit the attached work-around for Axes.cla?
> Instead of offsetting the title using Affine2D().translate( ... figure.dpi
> ... ), it uses ScaledTranslation( ... figure.dpi
> what do you mean by "range" parameter. What should this parameter actually
> do ?
>
Actually just pass it along to numpy.histogram(). I guess it just ignores
all data outside the range.
Cheers,
Olle
-
Check out the new
11 matches
Mail list logo
