devshift / jnativehook

Automatically exported from code.google.com/p/jnativehook
0 stars 0 forks source link

NativeKeyEvent.getKeyChar() does not work. #64

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.NativeKeyEvent.getKeyChar(); doesn't reply the right char.
2.
3.

What is the expected output? What do you see instead?
The char of the pressed Key, instead i only see a box for a non existiong 
character.

What version of the product are you using? On what operating system?
I'm using version 1.1.4 on windows 7 home

Please provide any additional information below.

Original issue reported on code.google.com by a7a7...@yahoo.de on 11 Aug 2013 at 4:07

GoogleCodeExporter commented 9 years ago
I need more information about your local language.  Please include all 
languages you currently have configured and what language is set when not 
information is displayed.

Original comment by a...@1stleg.com on 9 Sep 2013 at 10:41

GoogleCodeExporter commented 9 years ago
my local Language is German, but Englisch is installed aswell.

Original comment by a7a7...@yahoo.de on 23 Sep 2013 at 7:17

GoogleCodeExporter commented 9 years ago
There is a jar for developer preview 1 attached to Issue #67.  Although all of 
the code for NativeKeyEvent.getKeyChar() should be identical, I put in more 
robust logging to help identify issues.  Can you please execute the jar, 
duplicate the problem and paste the output from the command line?  I am 
particularly interested in the portion related to win_unicode_helper during the 
initialization process.  That should help me figure out exactly what is going 
on.

Original comment by a...@1stleg.com on 23 Sep 2013 at 8:21

GoogleCodeExporter commented 9 years ago
A lot of work has gone into the keychars for 1.2.  This should be working in 
the trunk at this time.  If you are still experiencing an issue please let me 
know.

Original comment by a...@1stleg.com on 12 May 2014 at 3:18