CODEWITHSUNDEEP
javamultithreadingswingawt
julianff
julianff

Reputation: 170

Java.awt.EventQueue.invokeLater() : Can't understand the syntax

I understand that EventQueue.invokeLater() is a function called to make the Java Swing components Thread-Safe. Also, I know that the argument to this function is an object with implements Runnable. However, I am unable to understand the syntax for this function call, i.e. this call - 

EventQueue.invokeLater(()-> {
        new Screen();
    });

Here, Screen() is a class that extends JFrame.

public class Screen extends JFrame
{   
    Screen()
    {    
        setSize(1000, 1000);
        JPanel j1 = new Board();
        j1.setBounds(0,0,500, 500);
        JPanel j2 = new DiceModel();
        j2.setBounds(500, 0, 500, 500);
        add(j1);
        add(j2);
        setLayout(null);
        setDefaultCloseOperation(EXIT_ON_CLOSE);
        setLocationRelativeTo(null);
        setVisible(true);
    }   

    public static void main(String[] args) 
    {
        EventQueue.invokeLater(()-> {
            new Screen();
        });

    }
}

This code runs as expected. Board and DiceModel are two classes I have defined that which extend JPanel.

The invocation 

EventQueue.invokeLater( new Screen() );

gives the expected error that Screen is not an object of type Runnable.

So,my question is, what is the meaning of the syntax for the function call for invokeLater() ? Is it a kind of anonymous function call in Java ?

Upvotes: 1

Views: 2256

Answers (1)

Madhusudan chowdary
Madhusudan chowdary

Reputation: 553

The complete Swing processing is done in a thread called EDT (Event Dispatching Thread). Therefore you would block the GUI if you would compute some long lasting calculations within this thread.

The way to go here is to process your calculation within a different thread, so your GUI stays responsive. At the end you want to update your GUI, which have to be done within the EDT. Now EventQueue.invokeLater comes into play. It posts an event (your Runnable) at the end of Swings event list and is processed after all previous GUI events are processed.

Also the usage of EventQueue.invokeAndWait is possible here. The difference is, that your calculation thread blocks until your GUI is updated. So it is obvious that this must not be used from the EDT.

Still there is Java code out there that starts a JFrame simple from the main thread. This could cause issues, but is not prevented from Swing. Most modern IDEs now create something like this to start the GUI

public static void main(String args[]) {
java.awt.EventQueue.invokeLater(new Runnable() {
    public void run() {
        new NewJFrame().setVisible(true);
       }
    });
 }

Upvotes: 1

Related Questions