On Tue, Oct 21, 2008 at 8:57 PM, Paul Ivanov <[EMAIL PROTECTED]> wrote:
> Here's an updated patch:
>
> I decided to go with 'c' and 'v'  for Back and Forward since these keys
> are in the same place on most localized keyboard layouts (sorry, dvorak
> users) (as JDH pointed out, I could not use 'z' and 'x' because 'x' is
> used as a modifier in Pan/Zoom mode)
>
> I've added a ReST table detailing all of the key bindings as per JDH's
> suggestion.

Thanks Paul, for the enhancements, and especially for doing the extra
work to document the functionality and test the docs.  Applied to svn
6291.  If you are inclined, we probably need an rc param or something
like that to determine which keys mpl responds to since, as we have
more of these, we increase the risk that we get in the way of
application developers embedding mpl.

Eg, in matplotlibrc, one could do

  toolbar.keys :  x, y, c, v, g, f, p, z, control, left, right  # with
docs describing what key does what

So the user could turn off any or all of these.  Then in
backend_bases, before we issue an event based on a key stroke, we
could check this default list to make sure the user wants mpl handling
these events.

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

Reply via email to