Ooops, I had forgotten to add the Wx backend. Here is a new patch.
By the way, with the wx backend, there seems to be a simple mistake in
the "show" method of the figure manager, to reproduce the traceback do
(with a recent ipython):
ipython -wthread -pylab
In [1]: f = figure()
In [2]: f.show()
Hi all,
A while ago (a year or so), I was looking for a ginput-like function with
matplotlib. For those who don't know what I am talking about, it is a
blocking call that can be used in a script to ask the user to enter
coordinnate by clicking on the figure. This is incredibly handy, as it
allows
Ok. I'll change this in SVN.
Nils Wagner wrote:
> On Tue, 29 Jan 2008 15:33:46 -0500
> Michael Droettboom <[EMAIL PROTECTED]> wrote:
>> Ok, to save me the trouble of installing Python-2.4 (which doesn't
>> feel like the culprit, but appears to be the only variable other than
>> platform) I see
I think it would be a shame to lose the current matplotlib 3d plotting
functionality, even if it's not ideal. I've found it very useful for
plotting small sets of data, and much more straightforward to use than
Mayavi or other vtk-based 3d plotting packages.
Having said that, I'm not volunteering
Ok, to save me the trouble of installing Python-2.4 (which doesn't feel
like the culprit, but appears to be the only variable other than
platform) I seem to recall a discussion on numpy about coercion of
scalars to Python int's that may be the culprit here. Can you please
add the following lin
Michael Droettboom skrev:
Interesting. I can't reproduce this with Python-2.5 on Linux. What
version of numpy do you have installed? Can you send your matplotlibrc
file?
I tried upgrading numpy to the latest svn version but I still see the
same problem. My matplotlibrc file is just the d
For some reason, when axis() is called, the "emit" flag (which
determines whether to update all of the shared axes) was being set to
False by default. There may be a good reason for this that I'm not
aware of, but it seems reasonably harmless, and doesn't break the
existing shared_axis example
Johann Cohen-Tanugi wrote:
> is basemap deferred as well? It is kinda 3D no?
I understand basemap is working reasonably well. But Jeff Whitaker
would know better than I.
> Second a color map or
> contour plot is kinda 2D either.. unless I am confusing what you
> mean by 2D : 2D in renderi
Interesting. I can't reproduce this with Python-2.5 on Linux. What
version of numpy do you have installed? Can you send your matplotlibrc
file?
Cheers,
Mike
Jörgen Stenarson wrote:
> Hi,
>
> I think there is a bug in the pdf backend (png-files save ok) that makes
> plots crash when they co
Yes, it is probably a good-sized chunk of work. In the recent
transforms overhaul, the 3d stuff was deferred, so it hasn't been
updated to use the new "way of doing things".
Just "getting it to work as it did before" is probably less work than
"rethinking what 3D means in the context of matplo
Hi,
I have problem setting the axis limits when using a twinx plot. I assume
it should be possible to set both x-axis limits after a pylab.twinx()
call by issuing only one call to pylab.axis.
The attached tries to plot the same figure in two different ways the
first way ends up with differen
Hi,
I think there is a bug in the pdf backend (png-files save ok) that makes
plots crash when they contain a marker.
The attached script crashes on the last savefig. I have also attached a
traceback.
I run matplotlib-svn-4904 on windows with python 2.4
/Jörgen
Traceback (most recent call
12 matches
Mail list logo
