Re: [matplotlib-devel] Triplot function problems

2010-07-05 Thread Ian Thomas
Hello again Alberto, On 4 July Alberto Azevedo wrote: When I use the triplot function with 100-1000 points it works well. The problem is that in my work I often use grids with 3-10 points. With those grids triplot takes a long time to compute (I never wait for the results, it takes

Re: [matplotlib-devel] Triplot function problems

2010-07-05 Thread John Hunter
On Mon, Jul 5, 2010 at 4:36 AM, Alberto Azevedo a...@netcabo.pt wrote: I'm really sorry for my comment, it was not my intention to offend anyone. You are absolutely right about that, therefore I would like to apologize to all developers, in particular to you, for my comment regarding the matlab

Re: [matplotlib-devel] Triplot function problems

2010-07-05 Thread John Hunter
On Mon, Jul 5, 2010 at 3:17 AM, Ian Thomas ianthoma...@googlemail.com wrote: Yes, it does indeed take a long time for large grids. The bottleneck is line 51 in lib/matplotlib/tri/triplot - I use the plot command which creates a separate Line2D object for each edge in the triangulation, and

[matplotlib-devel] show() is now more uniform across backends

2010-07-05 Thread Eric Firing
http://www.mail-archive.com/matplotlib-devel@lists.sourceforge.net/msg06691.html Looking back through mail, I noticed the above thread that was still hanging with respect to 1.0. A few minutes ago, in 8494, I went ahead and committed a change that makes show block in tkagg and fltkagg, just as

Re: [matplotlib-devel] Typo in mplconf

2010-07-05 Thread Benjamin Root
After some more digging, I think I finally found the source of my issues. I have noticed that there are inconsistencies between the keys and sections listed in the default matplotlib.conf file and in the class MPLConfig(). While in most cases, these inconsistencies are innocuous and do not cause

Re: [matplotlib-devel] Typo in mplconf

2010-07-05 Thread Eric Firing
On 07/05/2010 10:22 AM, Benjamin Root wrote: After some more digging, I think I finally found the source of my issues. I have noticed that there are inconsistencies between the keys and sections listed in the default matplotlib.conf file and in the class MPLConfig(). While in most cases,

Re: [matplotlib-devel] Typo in mplconf

2010-07-05 Thread Benjamin Root
On Mon, Jul 5, 2010 at 3:38 PM, Eric Firing efir...@hawaii.edu wrote: On 07/05/2010 10:22 AM, Benjamin Root wrote: After some more digging, I think I finally found the source of my issues. I have noticed that there are inconsistencies between the keys and sections listed in the default

Re: [matplotlib-devel] subplotting 3d figures

2010-07-05 Thread Benjamin Root
Just re-pinging to see if there is any interest in this patch. Ben Root On Sat, Jul 3, 2010 at 1:51 AM, Benjamin Root ben.v.r...@gmail.com wrote: Hello all, I have always been a bit troubled with how Axes3D object is a bit of a 2nd-class citizen in matplotlib. In particular, it is very