JDK-6680988 : KeyEvent is still missing VK values for many keyboards
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.4.0,6u5
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000,windows_xp
  • CPU: x86
  • Submitted: 2008-03-27
  • Updated: 2017-05-16
  • Resolved: 2011-05-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
6u10Fixed 7 b55Fixed
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
J2SE Version (please include all output from java -version flag):
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode, sharing)

Does this problem occur on J2SE 5.0.x or 6.0?  Yes / No (pick one)

Operating System Configuration Information (be specific):
Microsoft Windows XP [Version 5.1.2600]

Bug Description:
KeyEvent is still missing VK values for many keyboards.

This is related to RFE 4068241 and all the reports related to that one.

Using a Hebrew Keyboard the keys i) [, < Tav] ii) [. > Final Tzadeek] and iii) 
[; : Final Fay] all map to VK_UNDEFINED.

Likewise with a Danish Keyboard (and I assume also Norwegian) the keys for their last 
3 letters of the alphabet i) [ae] ii) [oe] iii) [aa] also all map to VK_UNDEFINED.

In the case of Hebrew the other Hebrew letters map to the English letters on the same 
key (like Alef maps to VK_T) which is fine, for the 3 problem keys there already mappings
to the English Symbols on the same key (for example using Hebrew [' " ,] maps to VK_COMMA)
so it would not help to make [, < Tav] map to VK_COMMA, as that would cause a Comma to be
typed instead of a Tav.

This makes Screen Recording and Playing back very difficult as these 6 keys (3 in each
language) can not be recorded.

EVALUATION This is clearly RFE. Actually, we already have a solution based on a different keymapping paradigm waiting to be used with jdk 1.5.0 update release. As soon as it will be verified, legally cleared and released, we are going to use it with JDK6 and 7. Idea is, to create a set of extended keycodes on startup of a user application. Thus the user will only operate with necessary set of keys, and there will be no need to invent and keep VK_ constants in KeyEvent for all possible national keyboards.

EVALUATION Since this change request about adding new VK_ constants into KeyEvent class, it looks like an RFE rather than a defect...