On 06/04/2010 02:25 PM, Daniele Nicolodi wrote:
> On 04/06/10 20:08, Michael Droettboom wrote:
>
>> Set rc.Params['path.simplify'] to False, or upgrade to 0.99.3.
>>
> Setting path.simplify = False solved my issue. Has been the issue solved
> in another way on 0.99.3 or path.simplify = Fa
Le jeudi 03 juin 2010 à 11:41 -0400, Jae-Joon Lee a écrit :
> On Wed, Jun 2, 2010 at 2:46 PM, Denis Laxalde wrote:
> > That would indeed be a better approach. Can somebody points me to the
> > particular methods/attributes to look at ?
> >
>
> As far as I can see, there is no public methods/attri
On 04/06/10 20:08, Michael Droettboom wrote:
> Set rc.Params['path.simplify'] to False, or upgrade to 0.99.3.
Setting path.simplify = False solved my issue. Has been the issue solved
in another way on 0.99.3 or path.simplify = False is simply the new default?
Thanks. Cheers,
--
Daniele
Set rc.Params['path.simplify'] to False, or upgrade to 0.99.3.
Mike
On 06/04/2010 02:04 PM, Daniele Nicolodi wrote:
> Hello.
>
> I'm observing a quite annoying behavior of matplotlib generated plots.
>
> I plot signal time series with continuous lines. When in those time
> series I have single po
Hello.
I'm observing a quite annoying behavior of matplotlib generated plots.
I plot signal time series with continuous lines. When in those time
series I have single points laying far from the median, those are not
represented on the plot. I think this must be due to the anti aliasing
algorithm,
By default, when the xy coordinate of the annotate is given in the
data coordinate, it draws the arrow only if the xy point is inside the
axes bbox. And, when the xy point is at the boundary of the axes bbox,
the inside-test results seems to depend on the backend. So, some
backends draws the arrow
Hello list,
I'm encountering a problem with annotate using the latest svn and GTKAgg-
backend.
I plot several annotate-arrows in my script, but some of them aren't saved to
the eps/pdf - file. More precisely the lower left arrow in the attached
example, who touches the lower (negative) boundary
Hello list;
I'm new to python/matplotlib, migrating from IDL. I need to do some
interactive point selection with mouse, and the pyplot.ginput() routine
seemed to be just the right thing here. I do however need to be able to
make a not previously specified number of clicks, so ginput(n=0) is a
req
On Tue, May 25, 2010 at 4:44 PM, Kaushik Ghose
wrote:
> Hi Gang,
>
> I don't know if it is a problem from nabble, but the 'archives' link from the
> main matplotlib pages goes to a decidedly non-matplotlib page.
>
> The link is http://www.nabble.com/matplotlib---users-f2906.html
Thanks -- I've up
On Fri, Jun 4, 2010 at 3:21 AM, Eric Firing wrote:
> On 05/25/2010 11:44 AM, Kaushik Ghose wrote:
>>
>> Hi Gang,
>>
>> I don't know if it is a problem from nabble, but the 'archives' link from
>> the
>> main matplotlib pages goes to a decidedly non-matplotlib page.
>>
>> The link is http://www.nab
Fixed in r8373.
Mike
On 06/03/2010 09:01 PM, Eric Firing wrote:
> On 06/03/2010 02:29 PM, Christoph Gohlke wrote:
>
>>
>> On 6/3/2010 5:20 PM, phob...@geosyntec.com wrote:
>>
-Original Message-
From: Christoph Gohlke [mailto:cgoh...@uci.edu]
Sent: Sunday, May 30,
On 05/25/2010 11:44 AM, Kaushik Ghose wrote:
> Hi Gang,
>
> I don't know if it is a problem from nabble, but the 'archives' link from the
> main matplotlib pages goes to a decidedly non-matplotlib page.
>
> The link is http://www.nabble.com/matplotlib---users-f2906.html
Evidently nabble has been r
12 matches
Mail list logo
