KeyPress::numberPadAdd, is this a bug?

General JUCE discussion
#1

I have a simple KeyListener class listening from a Component using Component::addKeyListener(). When I use any sign of my PC num pad, the Keypress.keyCode generated is 43 instaed 65643. What’s wrong?

1 Like
#2

Is NumLock active on your keyboard?

#3

With numLock enabled or disabled I have the same result hitting the + key. I tried in another laptop, and again the same. keyCode is always 43 instead 65643. However, [keypad] numbers work ok.

#4

Could somebody confirm if this is a bug? Jules?

#5

Hate to bump such old topics, but I’m having the exact same problem still on Windows 10. The actual ‘+’ key on my numpad gives a KeyPress int of 43. Checking against KeyPress::numberPadAdd doesn’t work.

2 Likes
#6

I also have this problem on Windows 10.

It seems that the value 43 is given by this line :

const UINT keyChar  = MapVirtualKey ((UINT) key, 2);

In the function doKeyDown() at juce_gui_basics\native\juce_win32_Windowing.cpp

#7

It seems that the numpad keys can directly give the value instead of the corresponding KeyPress::numberPad[something].

For example : when I use a KeyMappingEditorComponent and add a shortcut for a command with the ‘+’ key of my numpad, I get only “+” instead of “numpad +”.