|
Evaluation
|
Seems harmless enough to add another constant with the correct spelling.
xxxxx@xxxxx 1997-06-20
======================================================================
The same still exists as of JDK 1.3.
xxxxx@xxxxx 1999-12-09
As part of the AWT RFE cleanup effort, I am committing this to Merlin.
We may also want to deprecate the misspelled constant (this is what we
have done in the past).
xxxxx@xxxxx 1999-12-22
Added the new constant, but did not deprecate the old one.
xxxxx@xxxxx 2000-08-11
This bug has not been fixed quite properly.
See delta 1.43.1.2 for java/awt/event/KeyEvent.java:
229a230,234
>
> /**
> * This constant is obsolete, and is included only for backwards compatibility.
> * @see VK_SEPARATOR
> */
230a236,242
>
> /**
> * Constant for the Numpad Separator key.
> * @since 1.4
> */
> public static final int VK_SEPARATOR = VK_SEPARATER;
>
867c879
< case VK_SEPARATER: return Toolkit.getProperty("AWT.separater", "NumPad ,");
---
> case VK_SEPARATOR: return Toolkit.getProperty("AWT.separater", "NumPad ,");
^ ^
^ Fixed ok. ^ Not fixed.
String parameter "AWT.separater" in Toolkit.getProperty method
calling is misspelled.
xxxxx@xxxxx 2000-12-01
The property is not the public API, and really has nothing to do
with this bug.
However, it will be changed when the properties files are updated for 1.4
as part of 4379401.
xxxxx@xxxxx 2000-12-01
|