From: Tim L. <ti...@cs...> - 2005-04-13 14:33:53
|
On Wed, 13 Apr 2005, John Hunter <jdh...@ac...> wrote... > >>>>> "Tim" == Tim Leslie <ti...@cs...> writes: > > Tim> This all works fine except that the down key doesn't register > Tim> as released. After registering the down key press, no other > Tim> key events register until you hit the up key, at which point > Tim> the key release triggers for the up. > > It works fine for me -- what is your pygtk version and OS? > I'm using pygtk 2.2.0 on linux. AFAICT pygtk 2.0, this is running on ubuntu unstable. > > You might put some debug print statements to print event.keyval in > _get_key to see if an event is being triggered at the gtk level. OK, I'll have a play with that. > > Could it be a bad keyboard??? Yep :) Well, maybe. The down key works in every other app I use, but I've had problems with this keyboard in strange ways before, so I wouldn't put it past it. I'll try it out on another machine when I get a chance and see how it goes. It's a laptop, so I can't really change the keyboard. (hmm, maybe a usb external one, if I had one) > > Tim> I really don't know a lot about Gtk or the matplotlib > Tim> internals so I couldn't trace this bug deeper into the > Tim> libraries. Can anyone shed some light on what's going on? If > Tim> we can get the arrow keys working is there a chance of > Tim> getting them into the standard distribution (assuming we had > Tim> all backends working)? > > Absolutely. It might be nice to enable some standard keyboard > navigation too. OK well I'll play around with this some more and I'll get back to you once I have what I think is a complete, working patch. Cheers, Tim Leslie > > JDH > `- |