On Wed, Nov 26, 2008 at 10:59 AM, John Hunter <[EMAIL PROTECTED]> wrote:
> probably fairly easy using a class level attr in the MouseEvent. > Another possibility would be to add support for figure_enter_event, > figure_leave_event, axes_enter_event, axes_leave_event. The user code > would have to separately process the axes_leave_event but this might > be the cleanest solution. I am happy to add support for these ... I just committed axes/figure enter/leave event notifications, with example in examples/event_handling/figure_axes_enter_leave.py. If you register for a leave event, you will get passed the last event that was in your axes/figure before it left Everything is working well with one caveat -- a figure leave event is only triggered when you enter a new figure, not simply when you leave the figure. This is because I just used the existing mpl LocationEvents to support the new events, and none of these are created when you are not over a canvas. To properly handle the figure leave events, we will need to tap into the underlying GUI leave events. The axes leave events work fine, with the one caveat that if the axes region is [0,0,1,1] you may not see the leave event for the same reason you do not see the figure leave event until you are over another canvas. JDH ------------------------------------------------------------------------- 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 Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
