66 * implementations of the Abstract Window Toolkit. Subclasses of
67 * the <code>Toolkit</code> class are used to bind the various components
68 * to particular native toolkit implementations.
69 * <p>
70 * Many GUI events may be delivered to user
71 * asynchronously, if the opposite is not specified explicitly.
72 * As well as
73 * many GUI operations may be performed asynchronously.
74 * This fact means that if the state of a component is set, and then
75 * the state immediately queried, the returned value may not yet
76 * reflect the requested change. This behavior includes, but is not
77 * limited to:
78 * <ul>
79 * <li>Scrolling to a specified position.
80 * <br>For example, calling <code>ScrollPane.setScrollPosition</code>
81 * and then <code>getScrollPosition</code> may return an incorrect
82 * value if the original request has not yet been processed.
83 * <p>
84 * <li>Moving the focus from one component to another.
85 * <br>For more information, see
86 * <a href="http://java.sun.com/docs/books/tutorial/uiswing/misc/focus.html#transferTiming">Timing
87 * Focus Transfers</a>, a section in
88 * <a href="http://java.sun.com/docs/books/tutorial/uiswing/">The Swing
89 * Tutorial</a>.
90 * <p>
91 * <li>Making a top-level container visible.
92 * <br>Calling <code>setVisible(true)</code> on a <code>Window</code>,
93 * <code>Frame</code> or <code>Dialog</code> may occur
94 * asynchronously.
95 * <p>
96 * <li>Setting the size or location of a top-level container.
97 * <br>Calls to <code>setSize</code>, <code>setBounds</code> or
98 * <code>setLocation</code> on a <code>Window</code>,
99 * <code>Frame</code> or <code>Dialog</code> are forwarded
100 * to the underlying window management system and may be
101 * ignored or modified. See {@link java.awt.Window} for
102 * more information.
103 * </ul>
104 * <p>
105 * Most applications should not call any of the methods in this
106 * class directly. The methods defined by <code>Toolkit</code> are
|
66 * implementations of the Abstract Window Toolkit. Subclasses of
67 * the <code>Toolkit</code> class are used to bind the various components
68 * to particular native toolkit implementations.
69 * <p>
70 * Many GUI events may be delivered to user
71 * asynchronously, if the opposite is not specified explicitly.
72 * As well as
73 * many GUI operations may be performed asynchronously.
74 * This fact means that if the state of a component is set, and then
75 * the state immediately queried, the returned value may not yet
76 * reflect the requested change. This behavior includes, but is not
77 * limited to:
78 * <ul>
79 * <li>Scrolling to a specified position.
80 * <br>For example, calling <code>ScrollPane.setScrollPosition</code>
81 * and then <code>getScrollPosition</code> may return an incorrect
82 * value if the original request has not yet been processed.
83 * <p>
84 * <li>Moving the focus from one component to another.
85 * <br>For more information, see
86 * <a href="http://docs.oracle.com/javase/tutorial/uiswing/misc/focus.html#transferTiming">Timing
87 * Focus Transfers</a>, a section in
88 * <a href="http://java.sun.com/docs/books/tutorial/uiswing/">The Swing
89 * Tutorial</a>.
90 * <p>
91 * <li>Making a top-level container visible.
92 * <br>Calling <code>setVisible(true)</code> on a <code>Window</code>,
93 * <code>Frame</code> or <code>Dialog</code> may occur
94 * asynchronously.
95 * <p>
96 * <li>Setting the size or location of a top-level container.
97 * <br>Calls to <code>setSize</code>, <code>setBounds</code> or
98 * <code>setLocation</code> on a <code>Window</code>,
99 * <code>Frame</code> or <code>Dialog</code> are forwarded
100 * to the underlying window management system and may be
101 * ignored or modified. See {@link java.awt.Window} for
102 * more information.
103 * </ul>
104 * <p>
105 * Most applications should not call any of the methods in this
106 * class directly. The methods defined by <code>Toolkit</code> are
|