JDK-5099725 : AWT doesn't seem to handle MappingNotify events under X11.
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt
- Affected Version: 2.0,1.4.2_04
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: linux,solaris_9
- CPU: x86,sparc
- Submitted: 2004-09-09
- Updated: 2009-12-16
- Resolved: 2009-12-16
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.
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.
| JDK 7 |
|---|
7 b78Fixed  |
Related Reports
|
Relates :
|
Description
The easiest way to reproduce this is to login to a SunRay that has a US keyboard attached. Start up a simple Java application that puts up a TextField. Type a few letters. Then unplug the keyboard and plug in a non-US keyboard, eg., German. Type a letter that has a different location, such as the 'Y' on German that would be 'Z' on US. Note that a 'Z' still appears instead of 'Y'. After the keyboard is swapped on a SunRay, the first key that is pressed causes the X server to notice that the key event from the DTU has a different country code, so it reads in the description for that keyboard, remaps, and sends out a MappingNotify to interested clients. At that point AWT should refresh its notion of the keycode=>keysym mapping. ###@###.### 2004-09-09 ###@###.### 2004-09-10
Comments
|