[matplotlib-devel] Event handling example not working
I noticed on the event handling doc page: [email protected] that the draggable rectangle example doesn't work in version 0.98.3. The rectangle class no longer seems to have the xy property. If you replace the current on_press() method in the example with the code below it seem to work. def on_press(self, event): 'on button press we will see if the mouse is over us and store some data' if event.inaxes != self.rect.axes: return contains, attrd = self.rect.contains(event) if not contains: return xy = self.rect.get_x(),self.rect.get_y() print 'event contains', xy x0, y0 = xy self.press = x0, y0, event.xdata, event.ydata Neil - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Event handling example not working
Thanks - sorry for posting the mailing list address instead of the the event handling page(!). That'll teach me to email before proof-reading... 2008/10/29 Ryan May <[EMAIL PROTECTED]>: > Neil Crighton wrote: >> I noticed on the event handling doc page: >> >> [email protected] >> >> that the draggable rectangle example doesn't work in version 0.98.3. >> The rectangle class no longer seems to have the xy property. If you >> replace the current on_press() method in the example with the code >> below it seem to work. >> >> def on_press(self, event): >> 'on button press we will see if the mouse is over us and store >> some data' >> if event.inaxes != self.rect.axes: return >> >> contains, attrd = self.rect.contains(event) >> if not contains: return >> xy = self.rect.get_x(),self.rect.get_y() >> print 'event contains', xy >> x0, y0 = xy >> self.press = x0, y0, event.xdata, event.ydata >> > > Good catch. I checked in a slightly different version of the fix. > > Ryan > > -- > Ryan May > Graduate Research Assistant > School of Meteorology > University of Oklahoma > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Event handling example not working
*re-reads email* Apparently it won't teach me. Sorry for the spam. 2008/11/3 Neil Crighton <[EMAIL PROTECTED]>: > Thanks - sorry for posting the mailing list address instead of the the > event handling page(!). That'll teach me to email before > proof-reading... > > 2008/10/29 Ryan May <[EMAIL PROTECTED]>: >> Neil Crighton wrote: >>> I noticed on the event handling doc page: >>> >>> [email protected] >>> >>> that the draggable rectangle example doesn't work in version 0.98.3. >>> The rectangle class no longer seems to have the xy property. If you >>> replace the current on_press() method in the example with the code >>> below it seem to work. >>> >>> def on_press(self, event): >>> 'on button press we will see if the mouse is over us and store >>> some data' >>> if event.inaxes != self.rect.axes: return >>> >>> contains, attrd = self.rect.contains(event) >>> if not contains: return >>> xy = self.rect.get_x(),self.rect.get_y() >>> print 'event contains', xy >>> x0, y0 = xy >>> self.press = x0, y0, event.xdata, event.ydata >>> >> >> Good catch. I checked in a slightly different version of the fix. >> >> Ryan >> >> -- >> Ryan May >> Graduate Research Assistant >> School of Meteorology >> University of Oklahoma >> > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] mplot3d: thanks and buglet.
Reinier Heeres writes: > This is a known issue, and I hope to resolve it soon... > > Thanks for reporting though; if you notice any other problems, please > let me know! > > Regards, > Reinier > The 3d plotting is great, thanks for updating it! Another small bug: the plot_surface routine reveals bits that should be hidden behind foreground surfaces. You can see this in the test_surface() plot in demo.py Neil -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Patch adding minor ticks that autoscale
Hello, It has always bugged me that it's not easy to display minor ticks in matplotlib, and there is no easy way to make minor ticks autoscale the same way major ticks do. I just added a patch to tracker that (I hope!) fixes these two problems. https://sourceforge.net/tracker/?func=detail&aid=2789713&; group_id=80706&atid=560722 It adds a new locator class, AutoMinorLocator, that can be used to dynamically find minor tick positions based on major tick positions. It also adds a new function to pyplot, minorticks(), that can be used to toggle the minorticks on and off. Adding autoscaling minor ticks reduces performance, but not excessively (on my Intel centrino duo laptop). They should probably be off by default though. Any comments are welcome, Neil -- The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Tracker patch #2924245
Hi, I posted a patch that makes some small changes to minor tick autoscaling: http://sourceforge.net/tracker/? func=detail&aid=2924245&group_id=80706&atid=560722 If someone could check it's ok and apply it, that would be great. Cheers, Neil ___ http://www.astro.dur.ac.uk/~nhmc -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] plotting a series of 3D points and, picker=True and 3D
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 to make the 3d modules work with the new transforms :-/ Neil > > Message: 2 > Date: Tue, 29 Jan 2008 15:07:31 -0500 > From: Michael Droettboom <[EMAIL PROTECTED]> > Subject: Re: > To: Johann Cohen-Tanugi <[EMAIL PROTECTED]>, matplotlib > development list > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > 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 rendering or in data structure? > > I mean 2D in rendering -- matplotlib is fundamentally built on top of 2D > rendering APIs, which makes doing a lot of 3D things more > computationally expensive and less flexible than a dedicated 3D plotting > package. > > > Anyway, I am probably not the motivated individual to tackle this work, > > most of all because I do not know matplotlib internals, I am just a > > user, albeit with coding abilities. > > Well, anyone can jump in ;) Unfortunately, I probably don't have the > time for that now. I believe John Hunter has some more fully-formed > ideas about where 3D in matplotlib should go and where the best path may > be going forward. > > Cheers, > Mike > > > Michael Droettboom wrote: > >> 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 matplotlib", which is a > >> fundamentally 2D plotting environment. And there was some thinking > >> along the lines of "why bother with the former, if the latter may be > >> on the horizon?..." But I think it's going to take some motivated > >> individual to step up and do either of these. > >> > >> Cheers, > >> Mike > >> - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] A good, interactive plotting package
Another big difference between matplotlib and chaco: matplotlib has online documentation, examples and tutorials. I couldn't find any documentation on Chaco when I was looking around for a python plotting program. If I had, who knows, maybe I'd be using Chaco now instead of matplotlib :) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] A good, interactive plotting package
I did. But there's no manual, and the 'under construction' placeholders in the 'how do I?' and tutorial didn't give a great first impression. I see now there's a link to some example code, but it's a lot more intimidating than the matplotlib introductory stuff. > > Did you find http://code.enthought.com/chaco/ ? > > Not that we are trying to drive you away , we'd love to have you > stay. As I mentioned in my earlier post, when we migrate to traits > for matplotlib artist properties, we will get a pretty rich > interactive UI configuration layer. > > JDH > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Change in linestyle='steps' between 0.91 and 0.98
linestyle='steps' has changed behaviour between 0.91.2 and 0.98.3. The 'step' between two points used to move horizontally and then vertically from the left point neighbouring right point, now it moves vertically then horizontally. Was this change intentional? I hope not, because I've just spent the past hour working out it was the reason for my plotting routines not working properly :-/ Neil - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Change in linestyle='steps' between 0.91 and 0.98
Now I see there are more options in 0.98 - 'steps-pre', 'steps-post', 'steps-mid'. The default should be steps-post for backwards compatibility. In 0.98.3 the default is steps-pre. And sorry for the testy tone of the previous email :) Neil 2008/8/28 Neil Crighton <[EMAIL PROTECTED]>: > linestyle='steps' has changed behaviour between 0.91.2 and 0.98.3. The > 'step' between two points used to move horizontally and then > vertically from the left point neighbouring right point, now it moves > vertically then horizontally. > > Was this change intentional? I hope not, because I've just spent the > past hour working out it was the reason for my plotting routines not > working properly :-/ > > Neil > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ Matplotlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
