156 * default may not have an effect after installing the look and feel.
157 * Other look and feels may lazily access defaults so that a change to
158 * the defaults may effect an existing look and feel. Finally, other look
159 * and feels might not configure themselves from the defaults table in
160 * any way. None-the-less it is usually the case that a look and feel
161 * expects certain defaults, so that in general
162 * a {@code ComponentUI} provided by one look and feel will not
163 * work with another look and feel.
164 * <p>
165 * <strong>Warning:</strong>
166 * Serialized objects of this class will not be compatible with
167 * future Swing releases. The current serialization support is
168 * appropriate for short term storage or RMI between applications running
169 * the same version of Swing. As of 1.4, support for long term storage
170 * of all JavaBeans™
171 * has been added to the <code>java.beans</code> package.
172 * Please see {@link java.beans.XMLEncoder}.
173 *
174 * @author Thomas Ball
175 * @author Hans Muller
176 */
177 @SuppressWarnings("serial") // Same-version serialization only
178 public class UIManager implements Serializable
179 {
180 /**
181 * This class defines the state managed by the <code>UIManager</code>. For
182 * Swing applications the fields in this class could just as well
183 * be static members of <code>UIManager</code> however we give them
184 * "AppContext"
185 * scope instead so that applets (and potentially multiple lightweight
186 * applications running in a single VM) have their own state. For example,
187 * an applet can alter its look and feel, see <code>setLookAndFeel</code>.
188 * Doing so has no affect on other applets (or the browser).
189 */
190 private static class LAFState
191 {
192 Properties swingProps;
193 private UIDefaults[] tables = new UIDefaults[2];
194
195 boolean initialized = false;
|
156 * default may not have an effect after installing the look and feel.
157 * Other look and feels may lazily access defaults so that a change to
158 * the defaults may effect an existing look and feel. Finally, other look
159 * and feels might not configure themselves from the defaults table in
160 * any way. None-the-less it is usually the case that a look and feel
161 * expects certain defaults, so that in general
162 * a {@code ComponentUI} provided by one look and feel will not
163 * work with another look and feel.
164 * <p>
165 * <strong>Warning:</strong>
166 * Serialized objects of this class will not be compatible with
167 * future Swing releases. The current serialization support is
168 * appropriate for short term storage or RMI between applications running
169 * the same version of Swing. As of 1.4, support for long term storage
170 * of all JavaBeans™
171 * has been added to the <code>java.beans</code> package.
172 * Please see {@link java.beans.XMLEncoder}.
173 *
174 * @author Thomas Ball
175 * @author Hans Muller
176 * @since 1.2
177 */
178 @SuppressWarnings("serial") // Same-version serialization only
179 public class UIManager implements Serializable
180 {
181 /**
182 * This class defines the state managed by the <code>UIManager</code>. For
183 * Swing applications the fields in this class could just as well
184 * be static members of <code>UIManager</code> however we give them
185 * "AppContext"
186 * scope instead so that applets (and potentially multiple lightweight
187 * applications running in a single VM) have their own state. For example,
188 * an applet can alter its look and feel, see <code>setLookAndFeel</code>.
189 * Doing so has no affect on other applets (or the browser).
190 */
191 private static class LAFState
192 {
193 Properties swingProps;
194 private UIDefaults[] tables = new UIDefaults[2];
195
196 boolean initialized = false;
|