Chapter 14 Event-Driven Programming.ppt

Liang, Introduction to Java Programming, Sixth Edition, (c) 2007 Pearson Education, Inc. All rights reserved. 0-13-222158-6 Chapter 14 Event-Driven Programming Objectives To start with event-driven programming with a simple example (§14.1). To explain the concept of event-driven programming (§14.2). To understand events, event sources, and event classes (§14.2). To declare listener classes and write the code to handle events (§14.3). To register listener objects in the source object (§11.3). To understand how an event is handled (§14.3). To write programs to deal with ActionEvent (§14.3). To write programs to deal with MouseEvent (§14.4). To write programs to deal with KeyEvent (§14.5). To use the Timer class to control animations (§14.6 Optional). Procedural vs. Event-Driven Programming Procedural programming is executed in procedural order. In event-driven programming, code is executed upon activation of events. Taste of Event-Driven Programming The example displays a button in the frame. A message is displayed on the console when a button is clicked. Events An event can be defined as a type of signal to the program that something has happened. The event is generated by external user actions such as mouse movements, mouse clicks, and keystrokes, or by the operating system, such as a timer. Event Classes Event Information An event object contains whatever properties are pertinent to the event. You can identify the source object of the event using the getSource() instance method in the EventObject class. The subclasses of EventObject deal with special types of events, such as button actions, window events, component events, mouse movements, and keystrokes. Table 14.1 lists external user actions, source objects, and event types generated. Selected User Actions The Delegation Model Internal Function of a Source Component The Delegation Model: Example Selected Event Handlers java.awt.event.ActionEvent Inner Class Listeners A listener class is designed specificall