On 7/9/07, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> This change works for me under wx os OS X.
> I got the gui_paint idea from examples/dynamic_demo_wx.py. Replacing
> gui_paint with draw_idle seems to work okay there as well. I'll
> create a patch. Do you small patches like this on tracker as
On Mon, Jul 09, 2007 at 10:37:35AM -0500, John Hunter wrote:
> One minor bug I fixed for non wx backends in the (very cool)
> figure.canvas.mpl_connect("motion_notify_event",figure.canvas.hilite)
> functionality. gui_repaint is a wx only method, and I just commented
> it out and replaced the "draw
On 7/9/07, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 08, 2007 at 03:04:41AM -0400, Paul Kienzle wrote:
> > I submitted the 'contains' patch to the patch tracker on sourceforge.
>
> I've updated the 'contains' patch to handle figure enter/leave, at
> least on wx backends, and fixed a min
On Sun, Jul 08, 2007 at 03:04:41AM -0400, Paul Kienzle wrote:
> I submitted the 'contains' patch to the patch tracker on sourceforge.
I've updated the 'contains' patch to handle figure enter/leave, at
least on wx backends, and fixed a minor hit test bug in ellipse.
I've also removed the special
On Fri, Jul 06, 2007 at 05:31:58PM -0400, Paul Kienzle wrote:
> On Fri, Jul 06, 2007 at 10:15:48AM -0500, John Hunter wrote:
> > On 7/6/07, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> > > Instead I would like to start by splitting the current pick method
> > > into two parts:
> > >contains(event,
On Fri, Jul 06, 2007 at 10:15:48AM -0500, John Hunter wrote:
> On 7/6/07, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> > Instead I would like to start by splitting the current pick method
> > into two parts:
> >contains(event,picker) which returns truth value,details
> >pick(event) which gene
On Fri, Jul 06, 2007 at 10:15:48AM -0500, John Hunter wrote:
> On 7/6/07, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I've been playing with the pick infrastructure in 0.90 and find that
> > it doesn't meet my needs. The issue is that events from all artists
> > go to the same callback
On 7/6/07, Paul Kienzle <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've been playing with the pick infrastructure in 0.90 and find that
> it doesn't meet my needs. The issue is that events from all artists
> go to the same callback, so you are forced write your callback as a
> series of if statements fo
Hi,
I've been playing with the pick infrastructure in 0.90 and find that
it doesn't meet my needs. The issue is that events from all artists
go to the same callback, so you are forced write your callback as a
series of if statements for each artist which may receive a pick event.
I would rather
