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

2008-02-11 Thread Jack Sankey
; Jack replied to me offlist so I am going to paste in his post below. > Perhaps you and Gael can consult on the ideal functionality of ginput > vis-a-vis optional line segment drawing, etc... > > > > FromJack Sankey <[EMAIL PROTECTED]> > to John Hunter <[EMA

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

2008-02-08 Thread Paul Kienzle
On Fri, Feb 08, 2008 at 08:15:20AM +0100, Gael Varoquaux wrote: > On Thu, Feb 07, 2008 at 11:31:11AM -0500, Paul Kienzle wrote: > > There are two ways to do this in wx. > > > One is to use eventloop.Dispatch() which waits until the next available > > event: > > > [...] > > > The other is to

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

2008-02-07 Thread Gael Varoquaux
On Thu, Feb 07, 2008 at 11:31:11AM -0500, Paul Kienzle wrote: > There are two ways to do this in wx. > One is to use eventloop.Dispatch() which waits until the next available > event: > [...] > The other is to trigger a loop.Exit() from the click callback. > [...] Very nice. I am impre

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

2008-02-07 Thread Paul Kienzle
On Wed, Feb 06, 2008 at 01:21:30AM +0100, Gael Varoquaux wrote: > 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 trigg

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

2008-02-06 Thread Paul Kienzle
On Wed, Feb 06, 2008 at 01:21:30AM +0100, Gael Varoquaux wrote: > On Tue, Feb 05, 2008 at 07:16:59PM -0500, Paul Kienzle wrote: > > I'll look around some more and see if I can find the sleep until next > > event function in wx. > > Yeah, sleep, I need more of that. Or maybe you can find wx.coffee

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

2008-02-05 Thread Gael Varoquaux
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 >

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

2008-02-05 Thread Paul Kienzle
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

2008-02-05 Thread Gael Varoquaux
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

2008-02-05 Thread Paul Kienzle
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

2008-02-05 Thread Gael Varoquaux
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

2008-02-05 Thread Paul Kienzle
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] ginput: blocking call for mouse input

2008-02-05 Thread Gael Varoquaux
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

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

2008-02-05 Thread John Hunter
IL PROTECTED]> to John Hunter <[EMAIL PROTECTED]>, date Feb 5, 2008 4:02 PM subject Re: [matplotlib-devel] ginput: blocking call for mouse input mailed-by gmail.com Woa, it's working on GTKAgg using wx.Yield()? You must have added some voo

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

2008-02-05 Thread John Hunter
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

2008-02-02 Thread Gael Varoquaux
On Thu, Jan 31, 2008 at 04:41:41PM +0100, Gael Varoquaux wrote: > > If this seems like a good organization to you, I'll wait for a new > > patch and then contribute that. > Give me a few days, but it will come. Here is the new patch. I added visual feedback when accumulating points. I hope the do

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

2008-01-31 Thread Gael Varoquaux
On Thu, Jan 31, 2008 at 08:20:37AM -0600, John Hunter wrote: > As you know, this has been a much requested feature, I know. I have wanted it pretty badly. > and the hard part is to get something working across backends, which it > looks like you've done. Looks like it works OK. I would appreciat

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

2008-01-31 Thread John Hunter
On Jan 29, 2008 8:15 PM, Gael Varoquaux <[EMAIL PROTECTED]> wrote: > 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 recen

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

2008-01-29 Thread Gael Varoquaux
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()

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

2008-01-29 Thread Gael Varoquaux
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