Closed GoogleCodeExporter closed 9 years ago
The shortcuts are controlled by GTK itself - they are simply the default
mnemonics behaviour that GTK provides and as such I have no control over it.
Original comment by cdekter
on 15 Dec 2011 at 12:05
Bummer! Thanks anyway.
Original comment by tle...@gmail.com
on 15 Dec 2011 at 12:14
If you like you can file a bug against GTK and see what they say ;)
Original comment by cdekter
on 15 Dec 2011 at 12:16
So is the issue that GTK is unable to capture any Numpad keys at all, or it
won't recognize 1 and Numpad 1 as the same keystroke ? If it's the later,
could you not set up a listener to listen for both 1 or Numpad 1?
Original comment by tle...@gmail.com
on 15 Dec 2011 at 12:22
Not sure - have you tried it with Numlock on and off?
Original comment by cdekter
on 15 Dec 2011 at 12:28
Yes, with numlocks off the up/down/left/right arrows are used and the
highlighted selection moves up and down the menu.
Original comment by tle...@gmail.com
on 15 Dec 2011 at 12:31
Ah yes I see. Yes the bug is with GTK, it is not recognising number pad
numerals as mnemonics
Original comment by cdekter
on 15 Dec 2011 at 12:33
Let me clarify. When I turn numlocks ON, nothing happens on the folder menu,
it just stays open. When numlocks are OFF, the highlights move up/down in the
menu.
Does the Main Scripting UI window use the GTK library, or QT? When use "press
to capture" using numpad keys I get:
0 = <np_insert>
1 = <np_end>
2 = <np_down>
3 = <np_page_down>
4 = <np_left>
5 = <np_5>
6 = <np_right>
7 = <np_home>
8 = <np_up>
9 = <np_page_up>
These are the same whether numlocks are on/off. It seems that if you get any
<nm_*> events, you would check to see if numlocks are on/off and then act
accordingly.
Just some thoughts.
Original comment by tle...@gmail.com
on 15 Dec 2011 at 12:45
Original issue reported on code.google.com by
tle...@gmail.com
on 14 Dec 2011 at 11:58