suraj0208/jnativehook

Wrong Key Location For Numpad Enter Key

Closed this issue · 10 comments

write a sample code for public void nativeKeyPressed(NativeKeyEvent e)function 

Then 

if the user is pressing Numpad enter key then e.getKeyLocation() should returns 
4 (The location of numpad area), but its returning 1(The location of main 
keyboard area)

regards,
Rajeev

Original issue reported on code.google.com by rajeevmi...@gmail.com on 20 May 2013 at 7:23

  • Merged into: #57
Hi Rajeev,

Can you please provide your Operating System, Languages Used, Default Language 
and what type of keyboard you are using.

Thank you

Original comment by a...@1stleg.com on 18 Jun 2013 at 5:31

This is a deal breaker for me. Sorry but until this is fixed, I can't use it.

Tried it with US keyboard, US international keyboard, Japanese IME keyboard, 
and the on-screen keyboard from Windows' accessibility.

Tested all those keyboards on on Windows XP x86 NT6.1 and Windows XP x64 NT6.2

For whoever stumbles here too, I installed a keyboard hook with plain JNA and 
it does work, though it doesn't support mouse hooks (as of this date).
http://code.google.com/p/goldriver/source/browse/trunk/king/src/jnacontrib/w32ke
yhook/KeyHook.java?r=36

Original comment by mark.jeronimus@gmail.com on 22 Jul 2013 at 12:53

Found an undocumented workaround for the problem.  Should be fixed @738.

Original comment by a...@1stleg.com on 22 Jul 2013 at 5:46

  • Changed state: Fixed

Attachments:

It still gives the wrong location code when releasing.

I think you meant
kbhook->flags & 0x01
instead of 
kbhook->flags && 0x01

Original comment by mark.jeronimus@gmail.com on 22 Jul 2013 at 12:42

Original comment by a...@1stleg.com on 22 Jul 2013 at 3:51

  • Changed state: Verified

Original comment by a...@1stleg.com on 22 Jul 2013 at 3:51

  • Changed state: Started
Hi,

Sorry for late reply, here is the required information...
OS : Windows-7
Programming Language : Java
Keyboard : Most common keyboard with 101 keys


Original comment by rajeevmi...@gmail.com on 8 Aug 2013 at 5:38

Hi,

What are the changes you have done to fix this issue in the JAR provided above?

Thanks & Regards
Rajeev

Original comment by rajeevmi...@gmail.com on 8 Aug 2013 at 10:42

for changes, see Source on top of this page then go to Changes.

For updates about this, see issue 57(fixed) which is has a broader cover than 
this one.

Original comment by mark.jeronimus@gmail.com on 8 Aug 2013 at 11:38

Merging this issue with 57.  I will hopefully have a dev preview for 1.2 in 
another week.

Original comment by a...@1stleg.com on 8 Aug 2013 at 9:15

  • Changed state: Duplicate