Previous | Next | Trail Map | To 1.1 -- And Beyond! | GUI Changes: The AWT Grows Up


Writing a Component Listener

One or more component events are generated by a Component object just after the component is hidden, made visible, moved, or resized. An example of a component listener might be in a GUI builder tool that's displaying information about the size of the currently selected component, and that needs to know when the component's size changes. You shouldn't need to use component events to manage basic layout and rendering.

The component hidden and component visible events occur only as the result of calls to a Component's setVisible method (or its deprecated equivalents, show and hide). For example, a window might be miniaturized into an icon (iconified), without a component hidden event being generated.

Component Event Methods

The ComponentListener(in the API reference documentation) interface and its corresponding adapter class, ComponentAdapter(in the API reference documentation), contain four methods:
void componentHidden(ComponentEvent)
Called by the AWT after the listened-to component is hidden as the result of the setVisible method being called.

void componentMoved(ComponentEvent)
Called by the AWT after the listened-to component moves, relative to its container. For example, if a window is moved, the window generates a component moved event, but the components it contains do not.

void componentResized(ComponentEvent)
Called by the AWT after the listened-to component's size [rectangular bounds?] changes.

void componentShown(ComponentEvent)
Called by the AWT after the listened-to component becomes visible as the result of the setVisible method being called.

Examples of Handling Component Events

The following applet demonstrates component events. The applet brings up a window (Frame) that contains a label and a checkbox. The checkbox controls whether the label is visible. Whenever the applet starts up (such as when you visit or revisit the page containing the applet), the window is made visible. Whenever the applet stops (such as when you leave the page containing the applet), the window is hidden. A text area displays a message every time the window, label, or checkbox generates a component event.

Since you can't run the applet, here's a picture of it:


Try this:
  1. Click the checkbox to hide the label.
    The label generates a component hidden event.
  2. Click the checkbox again to show the label.
    The label generates a component shown event.
  3. Iconify and then deiconify the window labeled "SomeFrame".
    You do not get component hidden or shown events.
  4. Resize the window labeled "SomeFrame".
    You'll see component resized (and possibly component moved) events from all three components -- label, checkbox, and window. If the window's layout manager didn't make every component as wide as possible, the label and checkbox wouldn't have been resized.

You can find the applet's code in ComponentDemo.java. Here is the applet's component event handling code:

public class ComponentDemo ... implements ComponentListener {
    ...
    //where initialization occurs:
	someFrame = new SomeFrame(this);
    ...

    public void componentHidden(ComponentEvent e) {
	displayMessage("componentHidden event from "
		       + e.getComponent().getClass().getName());
    }

    public void componentMoved(ComponentEvent e) {
	displayMessage("componentMoved event from "
		       + e.getComponent().getClass().getName());
    }

    public void componentResized(ComponentEvent e) {
	displayMessage("componentResized event from "
		       + e.getComponent().getClass().getName());
    }

    public void componentShown(ComponentEvent e) {
	displayMessage("componentShown event from "
		       + e.getComponent().getClass().getName());
    }
}

class SomeFrame extends Frame ... {
    ...
    SomeFrame(ComponentListener listener) {
	...
	label.addComponentListener(listener);
	checkbox.addComponentListener(listener);
	this.addComponentListener(listener);
	...
    }
    ...
}

You can find more examples of component listeners in the following sections: [LIST GOES HERE]

The ComponentEvent Class

Each component event method has a single parameter: a ComponentEvent(in the API reference documentation) object. The ComponentEvent class defines a useful method, getComponent, which returns the Component that generated the event.


Previous | Next | Trail Map | To 1.1 -- And Beyond! | GUI Changes: The AWT Grows Up