[matplotlib-devel] Basemap.resolution

Hi, how about adding the possibility to give a Basemap instance to the resolution parameter when creating a new Basemap object, and to directly set some of its attributes (like coastsegs, cntrysegs, etc) thus preventing from computing them? It may be interesting when plotting several equavalent ma

Re: [matplotlib-devel] plotting a series of 3D points and, picker=True and 3D

On Jan 31, 2008 11:35 PM, Johann Cohen-Tanugi <[EMAIL PROTECTED]> wrote: > Actually, it seems that the following thread is also relevant to this > issue : [matplotlib-devel] merging sympy plotting stuff with matplotlib >

Re: [matplotlib-devel] Basemap.resolution

Stephane Raynaud wrote: > Hi, > > how about adding the possibility to give a Basemap instance to the > resolution parameter when creating a new Basemap object, and to > directly set some of its attributes (like coastsegs, cntrysegs, etc) > thus preventing from computing them? > It may be interestin

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Feb 2, 2008 8:48 AM, Gael Varoquaux <[EMAIL PROTECTED]> wrote: > Here is the new patch. I added visual feedback when accumulating points. > I hope the docstrings are clear. Great -- thanks again. I applied this patch and created a new example ginput_demo.py Tested on GTKAgg and TkAgg on my s

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Feb 5, 2008 3:58 PM, John Hunter <[EMAIL PROTECTED]> wrote: > On Feb 2, 2008 8:48 AM, Gael Varoquaux <[EMAIL PROTECTED]> wrote: > > > Here is the new patch. I added visual feedback when accumulating points. > > I hope the docstrings are clear. > > Great -- thanks again. I applied this patch and

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Tue, Feb 05, 2008 at 04:11:59PM -0600, John Hunter wrote: > Also, my version of GaelInput has seemed to stop evolving. This > version has the option to draw lines between clicks, which I use a > lot. Also, the default timeout is 0 now, since you can always > right-click to abort. You can still

[matplotlib-devel] backend_driver results in separate directories

Hi, I have a patch to post the results of examples/backend_driver.py to a backend specific directory, after first clearing the directory. Shall I commit? - Paul Index: backend_driver.py === --- backend_driver.py (revision

Re: [matplotlib-devel] backend_driver results in separate directories

Paul Kienzle wrote: > Hi, > > I have a patch to post the results of examples/backend_driver.py to > a backend specific directory, after first clearing the directory. Excellent idea. > > Shall I commit? Yes. Eric > > - Paul > > Index: backend_driver.py > ===

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Tue, Feb 05, 2008 at 03:58:08PM -0600, John Hunter wrote: > On Feb 2, 2008 8:48 AM, Gael Varoquaux <[EMAIL PROTECTED]> wrote: > > > Here is the new patch. I added visual feedback when accumulating points. > > I hope the docstrings are clear. > > Great -- thanks again. I applied this patch and

Re: [matplotlib-devel] backend_driver results in separate directories

On Tue, Feb 05, 2008 at 01:05:55PM -1000, Eric Firing wrote: > Paul Kienzle wrote: > > Hi, > > > > I have a patch to post the results of examples/backend_driver.py to > > a backend specific directory, after first clearing the directory. > > Excellent idea. > > > > > Shall I commit? > > Yes. D

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Tue, Feb 05, 2008 at 06:30:53PM -0500, Paul Kienzle wrote: > This failed for me in wx. > I posted a patch r4943 which moves flush_events from Figure to Canvas, > and removes the Yield in gui_repaint which caused an exception in wx. > The showfig callback in FigureManagerWx had an unreferenced

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Tue, Feb 05, 2008 at 11:23:14PM +0100, Gael Varoquaux wrote: > On Tue, Feb 05, 2008 at 04:11:59PM -0600, John Hunter wrote: > > Also, my version of GaelInput has seemed to stop evolving. This > > version has the option to draw lines between clicks, which I use a > > lot. Also, the default timeou

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Tue, Feb 05, 2008 at 06:46:19PM -0500, Paul Kienzle wrote: > In my applications I select multiple points from a particular line, > highlighting the point that will be selected as the mouse cursor moves. > I put a text message on the plot explaining what to do which disappears > when the selec

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Wed, Feb 06, 2008 at 12:38:32AM +0100, Gael Varoquaux wrote: > On Tue, Feb 05, 2008 at 06:30:53PM -0500, Paul Kienzle wrote: > > Setting the timeout to 0.01s for the busy loop in ginput seems excessive. > > Since it is waiting for human interaction, generally 0.1 seconds is good > > enough. > >

Re: [matplotlib-devel] ginput: blocking call for mouse input

On Tue, Feb 05, 2008 at 07:16:59PM -0500, Paul Kienzle wrote: > How about giving flush_events() an until=condition and timeout=n keywords > so that flush_events becomes: > if timeout > 0: set timer event which triggers out_of_time > while get next event: >process event >