Two simple questions:
1) How does one create a simple xy plot with a user-specified y-axis
range? Combination of setting kwargs ylim and autoscale_on doesn't seem
to do it ...
2) If I want to regenerate this plot with revised y data (but same
axes), what is the quickest option? At the momen
Michael Droettboom wrote:
> I'm assuming you're using the Agg backend. If so, you can get the raw
> memory wrapped in a Python buffer object as follows:
> figureCanvas.get_renderer().buffer_rgba(x, y)
> (where x, y is the upper left corner in the plot of the area you want to
> get.) It should
Sorry for the double sending, Giorgio. I got bitten by the Reply-To
bug for this list.
-- Forwarded message --
From: Angus McMorland <[EMAIL PROTECTED]>
Date: 30 Oct 2007 09:27
Subject: Re: [Matplotlib-users] (no subject)
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
On 23/10/2007,
>> And the harder question. I need access to the address of the raw image
>> buffer. (I assume this is a contiguous block of c-allocated memory?)
>> Presently, I copy into a ctypes buffer but this slows things down
>> significantly. Is there an alternative approach?
I'm assuming you're using th
Hi,
2007/10/29, Darran Edmundson <[EMAIL PROTECTED]>:
>
> I'm trying to generate plots as textures for use within a real-time
> graphics application (written using the pythonOgre graphics engine).
> I'm brand new to matplotlib so please bear with me. Two questions, one
> easy, one possibly hard.
I'm trying to generate plots as textures for use within a real-time
graphics application (written using the pythonOgre graphics engine).
I'm brand new to matplotlib so please bear with me. Two questions, one
easy, one possibly hard.
In the following code snippet, I create and draw a pie chart
On 10/29/07, Michael Droettboom <[EMAIL PROTECTED]> wrote:
> I submitted a fix for this in matplotlib SVN r4047. Freetype takes a
> FT_LOAD_FORCE_AUTOHINT flag to force it to bypass the patented bytecode
> hinter at runtime (even if it was compiled in). This appears to fix the
> problem, and doe
Le Monday 29 October 2007 10:57:52 Darren Dale, vous avez écrit :
> On Monday 29 October 2007 10:45:22 am Michael Droettboom wrote:
> > Darren Dale wrote:
> > > On Monday 29 October 2007 10:09:21 am Michael Droettboom wrote:
> > >> Michael Droettboom wrote:
> > >>> Darren Dale wrote:
> > I thi
On 10/21/07, nitriles <[EMAIL PROTECTED]> wrote:
>
> Hey, Ive got 10 strings of data that i plot into 1 big window, but somehow
> matplotlib gives me a very strange set-up. I am rather new to matplotlib and
> python so im kinda stuck now!
> heres an image of what i get and part of my code:
>
> http
Dear all,
is there the possiblity in matplolib to buind dendograms ?
I've searched a bit bout found no examples of it it seems not implemented
is there a plan for doing it ?
Thanks in advance for all reply
Giorgio-
This SF.net
Hey, Ive got 10 strings of data that i plot into 1 big window, but somehow
matplotlib gives me a very strange set-up. I am rather new to matplotlib and
python so im kinda stuck now!
heres an image of what i get and part of my code:
http://www.nabble.com/file/p13290670/Bildschirmphoto1.png
#
On Monday 29 October 2007 10:45:22 am Michael Droettboom wrote:
> Darren Dale wrote:
> > On Monday 29 October 2007 10:09:21 am Michael Droettboom wrote:
> >> Michael Droettboom wrote:
> >>> Darren Dale wrote:
> I think the problem is related to autohinting. When I compile
> freetype, the
Darren Dale wrote:
> On Monday 29 October 2007 10:09:21 am Michael Droettboom wrote:
>> Michael Droettboom wrote:
>>> Darren Dale wrote:
I think the problem is related to autohinting. When I compile freetype,
the patented bytecode and subpixel hinting support is disabled, I am
using
[My original response to the list got bounced because it included zip files. I
am posting again without the attachments.]
I attached the results (_b is with BROKEN = 0). I didn't notice any problems
in the Vera test, but in cmmi, Delta has problems when BROKEN is 1, it looks
better when BROKEN
On Monday 29 October 2007 10:09:21 am Michael Droettboom wrote:
> Michael Droettboom wrote:
> > Darren Dale wrote:
> >> I think the problem is related to autohinting. When I compile freetype,
> >> the patented bytecode and subpixel hinting support is disabled, I am
> >> using freetype's autohinting
Michael Droettboom wrote:
> Darren Dale wrote:
>> I think the problem is related to autohinting. When I compile freetype, the
>> patented bytecode and subpixel hinting support is disabled, I am using
>> freetype's autohinting instead. I recompiled freetype with the support for
>> the patented hi
Thanks for that. You really downplayed the problems when BROKEN is 1.
It seems to me that most of the glyphs are very bad -- the 'e', for
instance, is filled in the middle.
Darren Dale wrote:
> I think the problem is related to autohinting. When I compile freetype, the
> patented bytecode and
I should also mention -- please let me know if setting BROKEN to 0 fixes
any rendering problems.
Cheers,
Mike
Michael Droettboom wrote:
> Forgot to attach the program.
>
> Michael Droettboom wrote:
>> Nicolas, Darren,
>>
>> I have created a minimal program that hopefully will exercise the
>> p
Forgot to attach the program.
Michael Droettboom wrote:
Nicolas, Darren,
I have created a minimal program that hopefully will exercise the
problem. If it breaks for either of you, I'll take this to the freetype
mailing list for further clarification... If it doesn't break for you,
my theor
Nicolas, Darren,
I have created a minimal program that hopefully will exercise the
problem. If it breaks for either of you, I'll take this to the freetype
mailing list for further clarification... If it doesn't break for you,
my theory about the cause is still incorrect.
I have attached a sm
20 matches
Mail list logo
