GNOME Bugzilla – Bug 106913
shortcuts are broken on numerical keypad
Last modified: 2004-12-22 21:47:04 UTC
This may be a GTK issue. The shorcut usually associated to view->zoom->1:1 is set to the key "1". It does not work (numerical keypad). If I reset it to a letter, it works. If I reset it again to one of the figure of the numeric keypad (the menu displays "1" again), it is broken again. If I set it to the "*" of the numeric keypad, it works. I have noticed this with 1.3.11 also. OS is Mandrake 9.0, i.e. kernel 2.4.19, GTK/Glib 2.0.6 keyboard is a quite classical one (with the "window" key IIRC). I haven't found this in the opened-bug list, but might be wrong.
IIRC, this never worked on the numerical keypad. If at all this is a GTK+ issue. Did you look through the GTK+ bugs?
I have had a look at gtk bugs, but could not find anything like this there. IIRC, gimp 1.2 does work fine with the numeric keypad shortcut (I'll re-check tonight). But it makes a difference between the "1" and the numeric keypad "1". So I can redefine the function with numpad "1" and have what I want (I also redefine the "zoom out" to numpad "-" by the way, and this works fine in gimp 1.3.x) Gimp for Win32, on the other hand, does not make any difference between the classical "1" and the numpad "1".
GTK+-1.2 allowed you to assign for example KP_1 as a key shortcut while GTK+-2.2 seems to always interpret the 1 key on the keypad as 'End'. I'd say this is a bug and will reassign it to GTK+.
Just as a note to the GTK+ developers: This bug was originally filed against GIMP-1.3.
I confirm it is a GTK bug. I can see the same problem with Freecell. Although the shortcuts can be changed for some of the numeric keypad keys (the number), these do not work. The number on the top of the letters do work.
I change the summary from "do not work" to "are broken" for two reasons: 1- "do not work" suggests that it is impossible to set the shortcut to a key of the numeric keypad. It is possible to set thes keys as shortcut, and they appear in the gtk menus as such. But then, pressing the key has no effect. There is a real bug here, it is not just an enhancement or feature request. 2- "are broken" emphasizes more the fact that this is a regression, as it worked and was not broken in gtk 1.2
Wed May 21 12:52:01 2003 Owen Taylor <otaylor@redhat.com> * gtk/gtkkeyhash.[ch] (_gtk_key_hash_looku): We need to pass the unmasked state to gdk_keymap_translate_keyboard_state() to handle the case where a modifier not in the mask (like Num_Lock) changes the key value, so replace the masked state with a state/mask pair. (#106913, Olivier Ripoll) * gtk/gtkwindow.c gtk/gtkbinding.c: Update to pass in state/mask pair to _gtk_key_hash_lookup() Note that the keypad accelerators are distinct from the main keyboard, which I think is fine, but see bug 106913 for displaying them distinctly. Note also that the non-NumLock'ed keypad keys - KP_Up, etc, are mostly disallowed for unshifted accelerators since they are used for focus navigation.
Sorry, the display bug is bug 113458.
*** Bug 143206 has been marked as a duplicate of this bug. ***