Skip to main content

Java ActionListener Interface

Java ActionListener Interface

The Java ActionListener is notified whenever you click on the button or menu item. It is notified against ActionEvent. The ActionListener interface is found in java.awt.event package. It has only one method: actionPerformed().

actionPerformed() method

The actionPerformed() method is invoked automatically whenever you click on the registered component.

  1. public abstract void actionPerformed(ActionEvent e);  

How to write ActionListener

The common approach is to implement the ActionListener. If you implement the ActionListener class, you need to follow 3 steps:

1) Implement the ActionListener interface in the class:

  1. public class ActionListenerExample Implements ActionListener  

2) Register the component with the Listener:

  1. component.addActionListener(instanceOfListenerclass);  

3) Override the actionPerformed() method:

  1. public void actionPerformed(ActionEvent e){  
  2.            //Write the code here  
  3. }  

Java ActionListener Example: On Button click

  1. import java.awt.*;  
  2. import java.awt.event.*;  
  3. //1st step  
  4. public class ActionListenerExample implements ActionListener{  
  5. public static void main(String[] args) {  
  6.     Frame f=new Frame("ActionListener Example");  
  7.     final TextField tf=new TextField();  
  8.     tf.setBounds(50,50150,20);  
  9.     Button b=new Button("Click Here");  
  10.     b.setBounds(50,100,60,30);  
  11.     //2nd step  
  12.     b.addActionListener(this);  
  13.     f.add(b);f.add(tf);  
  14.     f.setSize(400,400);  
  15.     f.setLayout(null);  
  16.     f.setVisible(true);   
  17. }  
  18. //3rd step  
  19. public void actionPerformed(ActionEvent e){  
  20.             tf.setText("Welcome to Javatpoint.");  
  21. }  
  22. }  

output:

java awt button example 2

Java ActionListener Example: Using Anonymous class

We can also use the anonymous class to implement the ActionListener. It is the shorthand way, so you do not need to follow the 3 steps:

  1. b.addActionListener(new ActionListener(){  
  2. public void actionPerformed(ActionEvent e){  
  3.            tf.setText("Welcome to Javatpoint.");  
  4. }  
  5. });  

Let us see the full code of ActionListener using anonymous class.

  1. import java.awt.*;  
  2. import java.awt.event.*;  
  3. public class ActionListenerExample {  
  4. public static void main(String[] args) {  
  5.     Frame f=new Frame("ActionListener Example");  
  6.     final TextField tf=new TextField();  
  7.     tf.setBounds(50,50150,20);  
  8.     Button b=new Button("Click Here");  
  9.     b.setBounds(50,100,60,30);  
  10.   
  11.     b.addActionListener(new ActionListener(){  
  12.     public void actionPerformed(ActionEvent e){  
  13.             tf.setText("Welcome to Javatpoint.");  
  14.     }  
  15.     });  
  16.     f.add(b);f.add(tf);  
  17.     f.setSize(400,400);  
  18.     f.setLayout(null);  
  19.     f.setVisible(true);   
  20. }  
  21. }  

Output:

java awt button example 2


Anurag Rana Educator CSE/IT

Comments

Popular posts from this blog

Standard and Formatted Input / Output in C++

The C++ standard libraries provide an extensive set of input/output capabilities which we will see in subsequent chapters. This chapter will discuss very basic and most common I/O operations required for C++ programming. C++ I/O occurs in streams, which are sequences of bytes. If bytes flow from a device like a keyboard, a disk drive, or a network connection etc. to main memory, this is called   input operation   and if bytes flow from main memory to a device like a display screen, a printer, a disk drive, or a network connection, etc., this is called   output operation . Standard Input and Output in C++ is done through the use of  streams . Streams are generic places to send or receive data. In C++, I/O is done through classes and objects defined in the header file  <iostream> .  iostream  stands for standard input-output stream. This header file contains definitions to objects like  cin ,  cout , etc. /O Library Header Files There are...

locking

DBMS Locking Part I (DBMS only) TECHNICAL ARTICLES -> PERFORMANCE ARTICLES [  Back  ] [  Next  ] DBMS is often criticized for excessive locking – resulting in poor database performance when sharing data among multiple concurrent processes. Is this criticism justified, or is DBMS being unfairly blamed for application design and implementation shortfalls? To evaluate this question, we need to understand more about DBMS locking protocols. In this article, we examine how, why, what and when DBMS locks and unlocks database resources. Future articles will address how to minimize the impact of database locking. THE NEED FOR LOCKING In an ideal concurrent environment, many processes can simultaneously access data in a DBMS database, each having the appearance that they have exclusive access to the database. In practice, this environment is closely approximated by careful use of locking protocols. Locking is necessary in a concurrent environment to as...

DATA WAREHOUSE VERSUS DATA MART: THE GREAT DEBATE

DATA WAREHOUSE VERSUS DATA MART: THE GREAT DEBATE Customers exploring the field of business intelligence for the first time often lead with: What is the difference between a data warehouse and a data mart? The next question follows as predictably as night follows day: which one does my company need? Let me start by saying that the two terms are often confused. Indeed, some people in the industry use them virtually interchangeably, which is unfortunate, because they do reflect a valuable hierarchical difference. The Data Warehouse A "data warehouse" will typically contain the full range of business intelligence available to a company from all sources. That data consists of transaction-processing records, corporate and marketing data, and other business operations information; for example, a bank might include loans, credit card statements, and demand deposits data, along with basic customer information. This internal data is frequently combined with statistica...