A message to the users' list prompted me to begin a tirade about the default key bindings that appeared some time fairly recently--see the bottom of the matplotlibrc_template file. I really think that having these bindings enabled by default is a substantial mistake, one that will trip up and annoy far more users than it will help. I would like to class this as a bug, and remove default bindings from the maintenance branch and the trunk. Those users who want the bindings can then enable them via their own matplotlibrc files. Objections? Counter-arguments? Eric
On Mon, Jul 26, 2010 at 4:01 PM, Eric Firing <ef...@ha...> wrote: > A message to the users' list prompted me to begin a tirade about the > default key bindings that appeared some time fairly recently--see the > bottom of the matplotlibrc_template file. I really think that having > these bindings enabled by default is a substantial mistake, one that > will trip up and annoy far more users than it will help. > > I would like to class this as a bug, and remove default bindings from > the maintenance branch and the trunk. Those users who want the bindings > can then enable them via their own matplotlibrc files. > > Objections? Counter-arguments? > > Eric > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of 1ドル Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > I think, placing a global switch like keymap.enable = "no" would resolve this issue smoothly. The reason of putting key-bindings in the matplotlibrc file is to give users more freedom to create their own keymappings. As it is stated in that file, keybindings are easily nullified by assigning them to null strings. PS: Sorry, replying to all. -- Gökhan
On 07/26/2010 11:13 AM, Gökhan Sever wrote: > > > On Mon, Jul 26, 2010 at 4:01 PM, Eric Firing <ef...@ha... > <mailto:ef...@ha...>> wrote: > > A message to the users' list prompted me to begin a tirade about the > default key bindings that appeared some time fairly recently--see the > bottom of the matplotlibrc_template file. I really think that having > these bindings enabled by default is a substantial mistake, one that > will trip up and annoy far more users than it will help. > > I would like to class this as a bug, and remove default bindings from > the maintenance branch and the trunk. Those users who want the bindings > can then enable them via their own matplotlibrc files. > > Objections? Counter-arguments? > > Eric > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of 1ドル Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > <mailto:Mat...@li...> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > I think, placing a global switch like keymap.enable = "no" would resolve > this issue smoothly. The reason of putting key-bindings in the > matplotlibrc file is to give users more freedom to create their own > keymappings. As it is stated in that file, keybindings are easily > nullified by assigning them to null strings. Yes, I agree that a single setting to turn the mapping capability on or off would make sense. I strongly believe that by default it should be off. Eric > > PS: Sorry, replying to all. > > -- > Gökhan