Handling Standard AWT Events

[Listener/method maps]
This list is copied from the Java Tutorial. I have only listed common Components. A newer version which is more complete can be found at the UISwing Listener API Table

 

Listener Interface	Adapter Class	Interface Methods	Add Method
ActionListener	none	actionPerformed	addActionListener
AdjustmentListener	none	adjustmentValueChanged	addAdjuctmentListener
ComponentListener	ComponentAdapter	componentHidden componentMoved componentResized componentShown	addComponentListener
ContainerListener	ContainerAdapter	componentAdded componentRemoved	addContainerListener
FocusListener	FocusAdapter	focusGained focusLost	addFocusListener
ItemListener	none	itemStateChanged	addItemListener
KeyListener	KeyAdapter	keyPressed keyReleased keyTyped	addKeyListener
MouseListener	MouseAdapter	mouseClicked mouseEntered mouseExited mousePressed mouseReleased	addMouseListener
MouseMotionListener	MouseMotionAdapter	mouseDragged mouseMoved	addMouseMotionListener
TextListener	none	textValueChanged	addTextListener
WindowListener	WindowAdapter	windowActivated windowClosed windowClosing windowDeactivated windowDeiconified windowIconified windowOpened	addWindowListener

The AWT events described in the preceding table can be divided into two groups: low-level events and semantic events. Low-level events represent window-system occurrences or low-level input. Clearly, mouse and key events -- both of which result directly from user input -- are low-level events.

Component, container, focus, and window events are also low-level events. Component events let you track changes to a component's position, size, and visibility. Container events let you know when any component is added to or removed from a particular container. Focus events tell you when a component gains or loses the keyboard focus -- the ability to receive characters typed at the keyboard. Window events keep you informed of the basic status of any kind of Window, such as a Dialog or a Frame.

Mouse events are broken into two groups -- mouse motion events and all other mouse events -- so that an object can listen for mouse events such as clicks without requiring the system overhead necessary for generating and forwarding mouse motion events, which tend to occur frequently.

Semantic events include action, adjustment, item, and text events. These events are the result of component-specific user interaction. For example, a button generates an action event when the user clicks it, and a list generates an action event when the user doubleclicks an item in it. Adjustment events occur when a user somehow changes the value of a scrollbar. When a user selects an item in a group of items (such as a list), an item event is generated. Text events occur whenever the text in a text area or text field changes.