Windows Desktop Property Support

This feature involves two areas:

• Honor More User Preferences
  • Color Properties
  • Geometry Properties
  • Font Properties
  • Visual Effect Properties
  • Audio Feedback Properties
  • Input Properties
• Respond to Dynamic Changes

Honor More User Preferences

Most of the properties accessible via this method are specific to the Windows platform and hence have a "win." prefix. The list of supported Windows property names can be obtained programmatically by querying the "win.propNames" property:

 	String propnames[] = (String[])Toolkit.getDefaultToolkit().getDesktopProperty("win.propNames");
	System.out.println("Supported windows property names:");
	for(int i = 0; i < propnames.length; i++) {
	    System.out.println(propnames[i]);
	}

Properties which are supported on all platforms begin with an "awt." prefix.

Programs do not need to access these properties directly; the Windows look and feel will automatically read and interpret these properties to provide proper visuals and behavior for the components.

Color Properties

Geometry Properties

Font Properties

     java -Dswing.useSystemFontSettings=false MyJavaProgram

Visual Effect Properties

Audio-feedback Properties

Input Properties

Respond to Dynamic Changes

In 1.3, AWT added the ability to register for notification when one of these desktop property values changes. This is supported via the addPropertyChangeListener() method on java.awt.Toolkit. Swing's Windows Look and Feel will use this mechanism to watch for dynamic property change events on visual properties, and update the GUI by uninstalling and reinstalling the UI delegates in order for the components to have the most up-to-date visual property values. This dynamic behavior will automatically occur for all Swing programs running the Windows look and feel.

This mechanism will update GUI components by traversing the GUI hierarchy (starting with Frame.getFrames() and traversing all windows/containers/components from there). If a client has any undisplayable components when this occurs (see the isDisplayable() method on java.awt.Component for a definition of when a component is displayable), those components will not update automatically and it will be the client program's responsibility to update the UI on those components to ensure their Look and Feel is up-to-date. For example this occurs in the SwingSet2 demo because demo panels are created but not added to the GUI heirarchy until they are selected from the demo's tabbedpane. Therefore, before the newly selected demo panel is added to the hierarchy, it's UI is updated to ensure it has the most current property settings:

fragment from SwingSet2.java:
 
	// Ensure panel's UI is current before making visible
	JComponent currentDemoPanel = demo.getDemoPanel();
	SwingUtilities.updateComponentTreeUI(currentDemoPanel);

        // Replace current demo with newly selected demo
	demoPanel.removeAll();
	demoPanel.add(currentDemoPanel, BorderLayout.CENTER);