Sherif Ahmed wrote:
> Hello Mike,
>
> Thanks for your advice. I think this is exactly what I need. I am not sure
> how to use this option, might you help me?
>
> I use simply the following lines in my code:
>
> self.figure.clf()
> self.axes = self.figure.add_axes([0.1,0.1,0.8,0.8], projection='p
Hello Mike,
Thanks for your advice. I think this is exactly what I need. I am not sure
how to use this option, might you help me?
I use simply the following lines in my code:
self.figure.clf()
self.axes = self.figure.add_axes([0.1,0.1,0.8,0.8], projection='polar',
aspect='equal')
and later:
sel
I don't know the prehistory of GraphicsContext in matplotlib, but IMHO,
the issue here is that the matplotlib GraphicsContext class is just
badly named. All it is is a class to store a bunch of graphics
properties to be passed along to draw_path etc. to describe what is to
be drawn. It doesn'
Recently I realized that there is a potential problem in both the Cairo and the
Mac OS X backend related to how graphics contexts are handled. I tried your
example and found that the Mac OS X backend shows the same incorrect result as
the Cairo backend, which makes me suspect that this bug is r
Thanks for the report.
It seems that the clipping rectangles were applied additively, rather
than being set and removed for each axes.
This is now fixed in SVN.
Mike
Nathaniel Smith wrote:
> I ran into a very curious bug tonight, where if I
> -- had multiple axes in a figure
> -- and they
Sherif Ahmed wrote:
>
> Hello all,
>
> I am using matplotlib in order to generate a scientific drawing called
> “Smith Chart”. It consists of many shifted circles drawn in polar
> plot. This chart is widely used in electrical engineering field.
>
> I am facing a problem now with the new version
