Note that the KeyboardFocusManager itself implements KeyEventPostProcessor. By default, the current KeyboardFocusManager will be the final KeyEventPostProcessor in the chain. The current KeyboardFocusManager cannot be completely deregistered as a KeyEventPostProcessor. However, if a KeyEventPostProcessor reports that no further post-processing of the KeyEvent should take place, the AWT will consider the event fully handled and will take no additional action with regard to the event. (While it is possible for client code to register the current KeyboardFocusManager as a KeyEventPostProcessor one or more times, this is usually unnecessary and not recommended.) @author David Mendenhall @version 1.6, 11/17/05 @see KeyboardFocusManager#addKeyEventPostProcessor @see KeyboardFocusManager#removeKeyEventPostProcessor @since 1.4
|
|
|
|
|
|
|
|
|
|
|
|
|
|