matplotlib-users Mailing List for matplotlib

fred wrote:
> Hi,
> 
> My issue is quite simple: I reload several times an image
> with the colorbar enabled, and thus, I have several colorbars, not only one.
> 
> How can I disable this, and thus, get only one colorbar ?
> 
> Cheers,
> 
You may need to post a small code example so we can see what you are 
doing; but an interactive example using ipython -pylab may give you 
enough information to answer your question:
im = imshow(rand(20,20))
colorbar()
im.set_data(rand(20,20))
draw()
im.set_data(rand(20,20)*5)
im.autoscale() # to change the colormap limits
draw()
etc....
Eric

I can't figure why Polygons are used even when I simply draw lines.
But I know at least why I use empty list of vertices. ;)
In fact, I use matplotlib for a dynamic geometry software (something like
GeoGebra), and systematic use of high-level functions of matplotlib would be
to slow for that purpose.
And yet, I didn't want to use too low-level functions, like the renderer's
ones, for I didn't want to depend too much of a particular renderer.
So, I created once a set of plots and fills for every object, and then I
modified its attributes . I used to set its vertices to an empty list when I
didn't want it to appear on the figure.
I suppose now I'd better use instead something like.
 my_plot._visible = False
Nevertheless, I think empty vertices should be supported here (or not
supported at all for all renderers - for in 0.90.1 it still works with tkagg
for example)
Nicolas
On 6/6/07, John Hunter <jd...@gm...> wrote:
>
> On 6/6/07, Nicolas <nic...@ya...> wrote:
>
> > Unfortunately, I didn't use instantiated Polygon items myself, so for
> now I
> > can't figure which part of my code produces indirectly such empty
> > Polygons...
> >
> > May it be however possible to modify a little matplotlib code, so as to
> > assure the compatibility with the previous existing versions of
> matplotlib ?
> > Something like :
>
> I don't have a problem with this, but it just makes it easier for
> latent bugs in your code to remain hidden. Should we raise in the
> Polygon constructor is you pass in an empty list of vertices? Of
> course, you can always set xy directly, so this won't catch all the
> errors unless we use properties or traits.
>
> JDH
>

On 6/6/07, Nicolas <nic...@ya...> wrote:
> Unfortunately, I didn't use instantiated Polygon items myself, so for now I
> can't figure which part of my code produces indirectly such empty
> Polygons...
>
> May it be however possible to modify a little matplotlib code, so as to
> assure the compatibility with the previous existing versions of matplotlib ?
> Something like :
I don't have a problem with this, but it just makes it easier for
latent bugs in your code to remain hidden. Should we raise in the
Polygon constructor is you pass in an empty list of vertices? Of
course, you can always set xy directly, so this won't catch all the
errors unless we use properties or traits.
JDH

Thanks for doing this Russell; it installed, imported, and confirmed 
version fine on my Intel Mac (but I haven't actually had a chance to 
"use" it yet).
DG
Chr...@no... wrote:
> David,
>
> Can you test this?
>
> -CHB
>
>
> -------- Original Message --------
> Subject: [Matplotlib-users] matplotlib 0.90.1 binary installer for Mac
> Date: 2007年6月04日 14:19:18 -0700
> From: Russell E. Owen <ro...@ce...>
> Organization: University of Washington
> To: mat...@li...
>
> I've built a binary installer for matplotlib 0.90.1 for Mac that
> includes support for:
> - TkAgg that works with a user-installed Aqua Tcl/Tk (unlike the
> standard build) or the standard old Tcl/Tk from Apple
> - WXAgg using wxPython 2.8.
>
> I've only checked WXAgg and TKAgg on my PPC Mac. If anyone could test it
> on an Intel Mac I would be grateful.
>
> For now you can get it here:
> <http://www.astro.washington.edu/rowen/pythonpackages/>
>
> In the long run it will be available here:
> <http://pythonmac.org/packages/py25-fat/index.html>
>
> -- Russell
>
> P.S. Build instructions are here:
> <http://www.astro.washington.edu/rowen/BuildingMatplotlibForMac.html>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
> 
-- 
ERD/ORR/NOS/NOAA <http://response.restoration.noaa.gov/emergencyresponse/>

On 6/6/07, Matthias Michler <Mat...@gm...> wrote:
> By the way: What do you think about the "insert a 'l' or 'g' into your TextBox
> and get a grid or log-scale"-issue? Is there a possibility to switch the
> mpl-meaning of 'l', 'g' and 'f' off?
Yes, this is clearly an issue that has to be dealt with in a cleanup.
The current implementation has no concept of whether the text box is
the active widget. We would need to do something like activate the
text box when you click on it (and figure out the right cursor
location based on the click if there is already text in there) and
deactivate it on a carriage return or click in another axes. The
current implementation was only a proof of concept.
JDH

Hello John,
first of all thank you very much for adding this patch.
By the way: What do you think about the "insert a 'l' or 'g' into your TextBox 
and get a grid or log-scale"-issue? Is there a possibility to switch the 
mpl-meaning of 'l', 'g' and 'f' off?
best regards, 
Matthias 
On Wednesday 06 June 2007 16:19, John Hunter wrote:
> On 6/6/07, Matthias Michler <Mat...@gm...> wrote:
> > Some time ago I posted a suggestion to that (subject: 'additional key
> > events'), which may be got lost among the lots of mpl-mails.
> > I just send the patch once more, because I think it would be helpful
> > for such a prompt.
>
> Thanks for the reminder -- this is indeed a useful patch. I just
> committed it.
>
> I'd like to do a few enhancements to the text box widget and then add
> it to svn.
>
> JDH

On 6/5/07, Erik Wickstrom <er...@er...> wrote:
> ax = fig.add_subplot(111)
> #from pylab import *
> N = 7
> menMeans = (20, 35, 30, 35, 27, 21, 60)
> ind = arange(N) # the x locations for the groups
> #print ind
> width = 0.35 # the width of the bars
> ax = bar(ind, menMeans, width, color='b')
You have commented out the line 'from pylab import *' which is the
right thing for a web app server. But then you wrote
ax = bar(ind, menMeans, width, color='b')
which should raise a NameError because bar is defined in the pylab
namespace. So it looks like somewhere in your code which you are not
showing to us you have imported from pylab, which is wrong. What you
want to do is
ax = fig.add_subplot(111)
ax.bar(ind, menMeans, width, color='b')
and after that, read the user's guide, tutorial,
the FAQ http://matplotlib.sourceforge.net/faq.html#OO, and the API
tutorial http://matplotlib.sourceforge.net/leftwich_tut.txt <wink>
JDH

On 6/6/07, Matthias Michler <Mat...@gm...> wrote:
> Some time ago I posted a suggestion to that (subject: 'additional key
> events'), which may be got lost among the lots of mpl-mails.
> I just send the patch once more, because I think it would be helpful
> for such a prompt.
Thanks for the reminder -- this is indeed a useful patch. I just
committed it.
I'd like to do a few enhancements to the text box widget and then add
it to svn.
JDH

Hello everybody,
first of all I want to thank John for his work on the textbox - it really 
looks better than mine.
On Tuesday 05 June 2007 19:16, Mark Bakker wrote:
> I just saw in the code:
> if event.key is None: # simulate backspace
> So it works properly,
> Mark
In my opinion it would be a better soluton to generally add some more 
key-events (e.g. enter and backspace) than to simulate backspace with 
all 'None'-keys.
Some time ago I posted a suggestion to that (subject: 'additional key
events'), which may be got lost among the lots of mpl-mails. 
I just send the patch once more, because I think it would be helpful 
for such a prompt.
best regards,
Matthias
> On 6/5/07, Mark Bakker <ma...@gm...> wrote:
> > I notice the alignment problem.
> > But it looks like you are close.
> > On my machine (win32), the 'enter' key didn't work either. It works like
> > a backspace. That sounds like what Matthias reported.
> > Mark
> >
> > On 6/5/07, John Hunter <jd...@gm...> wrote:
> > > On 6/5/07, John Hunter <jd...@gm...> wrote:
> > > > I worked on this some time ago, I never got to the point where I
> > > > thought it was ready for production but it is close. There is a
> > > > problem if usetex is enabled, because partial tex strings will cause
> > > > errors. But you can use it with regular text or plain text.
> > >
> > > Typo: "plain text" was meant to be "math text"
> > >
> > > Now I remember what really bothered me about this widget, and it
> > > wasn't just the usetex problem. The problem is that mpl has three
> > > different vertical alignment methods for text: top, bottom and center.
> > > None of them are right for a text box: you want baseline. Try typing
> > > "thinking" into the text box and watch what happens when you add and
> > > remove the "g". We do need to support baseline alignment for text, so
> > > if someone has an interest in adding this it would be a very useful
> > > feature, not just for a text box for for text alignment (eg tick
> > > labels) in general.
> > >
> > > See the image of the "g" at
> > > http://freetype.sourceforge.net/freetype2/docs/glyphs/glyphs-3.html
> > > for a visual representation -- hwat I am calling the "baseline" they
> > > refer to as the "origin" in that graph. Our default alignment should
> > > be "origin" or "baseline" but we don't have support for that.
> > >
> > > JDH

Hi,
 Back with same problem when embedding in gtk.
 I would like to enable the key pressed event (key '1' '2' 'a' 'g' .. )
of NavigationToolbar2 in my pyGTK app.
 (These keys shortcut are described here: (or see PS of this email)
http://sourceforge.net/tracker/index.php?func=detail&aid=1432252&group_id=80706&atid=560722
 )
The shorcuts work perfectly using pylab. But when I include matplotlib
in my pyGTK app the shorcuts are broken. Example of the two version
(pylab: two_scales.py and pygtk: two_scales_embedded_in_gtk2 ) are
attached to this email.
 How could I manage to make them work ?
Thanks for your help.
David
PS
"""
NavigationToolbar2 now manages overlapping axes correctly
when the axes overlap like in two_scales.py,
NavigationToolbar2 only managed one axe.
For example, when zooming or panning, only the left y
scale will move.
With the patch, both axes will move.
It is also possible to select only one axe by
pressing a digit.
pressing '1' will enable navigation (set_navigate())
only on the first axe under the cursor.
pressing '2' will enable navigation only on the
second axe under the cursor.
Also, the LocationEvent.inaxes will behave
accordingly. For example, pressing 'g' will enable
the grid on the selected axe.
pressing 'a' will reenable all axes under the cursor.
"""

Hi folks,
I have a marker on a plot that is 5 units long, if I
resize the figure, the markers don't get resized
appropriately. How do I address this?
code snippet to display markers:
self.axes.annotate("text", xy=(0.5, 0.5), 
 
markerprops=dict(marker=TICKRIGHT,
markerfacecolor='black', markersize=5, 
 markeredgecolor='black',
markeredgewidth = 2),)
-iyer
 
____________________________________________________________________________________
Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online.
http://smallbusiness.yahoo.com/webhosting