71 * children with special decorations, such as a highlighted title bar. The
72 * active Window is always either the focused Window, or the first Frame or
73 * Dialog that is an owner of the focused Window.
74 * <p>
75 * The KeyboardFocusManager is both a centralized location for client code to
76 * query for the focus owner and initiate focus changes, and an event
77 * dispatcher for all FocusEvents, WindowEvents related to focus, and
78 * KeyEvents.
79 * <p>
80 * Some browsers partition applets in different code bases into separate
81 * contexts, and establish walls between these contexts. In such a scenario,
82 * there will be one KeyboardFocusManager per context. Other browsers place all
83 * applets into the same context, implying that there will be only a single,
84 * global KeyboardFocusManager for all applets. This behavior is
85 * implementation-dependent. Consult your browser's documentation for more
86 * information. No matter how many contexts there may be, however, there can
87 * never be more than one focus owner, focused Window, or active Window, per
88 * ClassLoader.
89 * <p>
90 * Please see
91 * <a href="http://java.sun.com/docs/books/tutorial/uiswing/misc/focus.html">
92 * How to Use the Focus Subsystem</a>,
93 * a section in <em>The Java Tutorial</em>, and the
94 * <a href="../../java/awt/doc-files/FocusSpec.html">Focus Specification</a>
95 * for more information.
96 *
97 * @author David Mendenhall
98 *
99 * @see Window
100 * @see Frame
101 * @see Dialog
102 * @see java.awt.event.FocusEvent
103 * @see java.awt.event.WindowEvent
104 * @see java.awt.event.KeyEvent
105 * @since 1.4
106 */
107 public abstract class KeyboardFocusManager
108 implements KeyEventDispatcher, KeyEventPostProcessor
109 {
110
111 // Shared focus engine logger
|
71 * children with special decorations, such as a highlighted title bar. The
72 * active Window is always either the focused Window, or the first Frame or
73 * Dialog that is an owner of the focused Window.
74 * <p>
75 * The KeyboardFocusManager is both a centralized location for client code to
76 * query for the focus owner and initiate focus changes, and an event
77 * dispatcher for all FocusEvents, WindowEvents related to focus, and
78 * KeyEvents.
79 * <p>
80 * Some browsers partition applets in different code bases into separate
81 * contexts, and establish walls between these contexts. In such a scenario,
82 * there will be one KeyboardFocusManager per context. Other browsers place all
83 * applets into the same context, implying that there will be only a single,
84 * global KeyboardFocusManager for all applets. This behavior is
85 * implementation-dependent. Consult your browser's documentation for more
86 * information. No matter how many contexts there may be, however, there can
87 * never be more than one focus owner, focused Window, or active Window, per
88 * ClassLoader.
89 * <p>
90 * Please see
91 * <a href="http://docs.oracle.com/javase/tutorial/uiswing/misc/focus.html">
92 * How to Use the Focus Subsystem</a>,
93 * a section in <em>The Java Tutorial</em>, and the
94 * <a href="../../java/awt/doc-files/FocusSpec.html">Focus Specification</a>
95 * for more information.
96 *
97 * @author David Mendenhall
98 *
99 * @see Window
100 * @see Frame
101 * @see Dialog
102 * @see java.awt.event.FocusEvent
103 * @see java.awt.event.WindowEvent
104 * @see java.awt.event.KeyEvent
105 * @since 1.4
106 */
107 public abstract class KeyboardFocusManager
108 implements KeyEventDispatcher, KeyEventPostProcessor
109 {
110
111 // Shared focus engine logger
|