-
Bug
-
Resolution: Not an Issue
-
P2
-
None
-
1.4.0
-
sparc
-
solaris_8
This attached application demonstrates problems getting KeyEvents in JDK 1.4.0
with a window spanning the entire physical screen. These problems don't exist
in JDK 1.3.1.
When invoked with no arguments, a full screen Frame with borders is
constructed. Typing any key should print out the message "got keyPressed"
and the application should exit. This works in JDK 1.3.1, but in JDK 1.4.0
the mouse must be clicked in the window before it responds to the
keyboard.
When invoked with the single argument "noborder", a full screen Window with
a Frame as its owner is constructed instead. In JDK 1.3.1 typing any key
will print out the message and exit the application. In JDK 1.4.0 there is
no response to any keyboard input even after clicking the mouse in the
window. The application must be killed from another screen.
This can be reproduced on Solaris/CDE and Windows 2000.
with a window spanning the entire physical screen. These problems don't exist
in JDK 1.3.1.
When invoked with no arguments, a full screen Frame with borders is
constructed. Typing any key should print out the message "got keyPressed"
and the application should exit. This works in JDK 1.3.1, but in JDK 1.4.0
the mouse must be clicked in the window before it responds to the
keyboard.
When invoked with the single argument "noborder", a full screen Window with
a Frame as its owner is constructed instead. In JDK 1.3.1 typing any key
will print out the message and exit the application. In JDK 1.4.0 there is
no response to any keyboard input even after clicking the mouse in the
window. The application must be killed from another screen.
This can be reproduced on Solaris/CDE and Windows 2000.