I just updated to the latest svn, and unveiled a bug that's evident
when using mixed-mode rendering in the PDF backend. I'm suspect I'm
the only one running my patch that enables set_rasterized on a
per-artist basis, so I'm the only one that's seeing it. :) Artists
that are left in vector mode are
On Thu, 19 Feb 2009, Michael Droettboom wrote:
> The drawing and then clipping is normal behavior. All of the backend formats
> have the ability to clip out arbitrary regions for drawing, so we take
> advantage of that rather than doing our own geometric clipping algorithm.
> The latter is a
Michael Droettboom schrieb:
> Gael,
>
> You raise a very good point about the duplication of code around. As a
> case in point, the patches you provided no longer apply to the
> "canonical" (or at least original) versions of the plugins that began
> life in matplotlib. Recent versions of Sphi
Gael Varoquaux schrieb:
> Hi all,
>
> Sorry for the multiple posting, this concerns various groups, and I'd
> rather the information not be lost.
>
> While working on getting our in-lab library ready to be merged with NiPy,
> I ran into some sort of 'sphinx extension mess' where various sphinx
>
a writes:
> Michael Droettboom writes:
> >
> > Thanks for the pointers.
> >
> > The original simplification code was written by John Hunter (I believe),
> > and I don't know if it was designed by him also or is a replication of
> > something published elsewhere. So I take no credit for and have l
Olle Engdegård wrote:
>
> Sorry for not being clear enough.
>
> I see this only when exporting to svg, importing it to Inkscape and
> then saving as pdf there. Never interactively. And never if exporting
> directly to pdf from matplotlib.
>
> It could very well be a bug in Inkscape, but matplotli
Sorry for not being clear enough.
I see this only when exporting to svg, importing it to Inkscape and then
saving as pdf there. Never interactively. And never if exporting directly
to pdf from matplotlib.
It could very well be a bug in Inkscape, but matplotlib is still saving
data that shou
I take this back -- I hadn't read your initial bug very carefully.
If Inkscape is rendering the SVG correctly, but it's PDF output is not
correct, then that seems like an Inkscape bug or a PDF viewer bug --
there's not too much we could do on the matplotlib end.
When you say you see it in WXAgg
On Wed, Feb 18, 2009 at 2:43 PM, James Evans wrote:
> All,
>
> I have just submitted a first-cut at a unit-test harness. The unit-tests
> do require the use of the 'nose' python module.
> Everything has been placed in the 'test' directory off of the root trunk
> branch. There is a README file w
I see it with 0.98.5.x, but not with SVN trunk. I'll look into this
further and see what I can determine.
Mike
Olle Engdegård wrote:
> On Wed, 18 Feb 2009, Joshua Lippai wrote:
>
>> Interesting. I can't reproduce your result using either the MacOSX or
>> WXAgg backend. Which backend are you
10 matches
Mail list logo
