-
Enhancement
-
Resolution: Fixed
-
P2
-
5.0u14
-
b01
-
x86
-
windows
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2202935 | 7 | Yuri Nesterenko | P4 | Closed | Duplicate | |
| JDK-2156093 | 6-pool | Yuri Nesterenko | P3 | Closed | Won't Fix | |
| JDK-2156636 | 6u10 | Yuri Nesterenko | P3 | Resolved | Fixed | b09 |
There should be a way for Java programmer to obtain an unique identifier for a key pressed. Presently, we only have certain part of keys covered by VK_* java keycodes. Sometimes a KEY_PRESSED/KEY_RELEASED is completely useless, with all fields filled with zeroes.
A proper solution to this would be manifold involving addition of more keycodes and providing means to query a KeyEvent about (in some sense) raw keycodes. However all this would require API change and is possible only in a new release (jdk7 I presume).
There should be a way to make a partial fix suitable for an update release, without API change.
A proper solution to this would be manifold involving addition of more keycodes and providing means to query a KeyEvent about (in some sense) raw keycodes. However all this would require API change and is possible only in a new release (jdk7 I presume).
There should be a way to make a partial fix suitable for an update release, without API change.
- backported by
-
JDK-2156636 provide raw key code from underlying system without changing API.
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-6678061 undefined keycodes for certain keyboard layouts
-
- Resolved
-
-
-
- Open
-