GUI thread safety issues

lrever

In jdk5.0 sun, in order to ensure that the GUI code is created from a thread other than the event dispatch thread, it is recommended to use two methods defined by the SwingUtilties class: invokeAndWait () or invokeLater (), such as:
import java.awt. *;
import javax.swing. *;
public class JLabelDemo extends JApplet {
  public void init ()
    try {
        SwingUtilites.invokeAndWait (
           new Runnable () {
           public void run () {
               makeGUI ();
                              }
                                  }
      );
} catch (Exception e) {
            System.out.println ("Can't create" + e);
}
}
     private void makeGUI () {
        ImageIcon ii = new ImageIcon ("xxx.gif");
        JLabel jl = new JLabel ("France", ii, JLabel.CENTER);
        add (jl);
   }
}
_____________________________________________________________
Could you write it as:
  Synchronized private void makeGUI () {
  While not using nvokeAndWait () ??? /

lrever

Could you write it as:
  Synchronized private void makeGUI () {
  Also without invokeAndWait () ??? /

lrever

Top yourself

lrever

Why is there no answer? Doesn't everyone need invokewait()?

seakey

InvokeAndWait() or invokeLater() is a concept of dispatching thread and thread synchronization~
Can it be written as:
  Synchronized private void makeGUI(){
  Also don't use nvokeAndWait() ???/
You can implement a thread to complete this function yourself, but don’t you find it troublesome to achieve the functions of the two provided methods? And do you add Synchronized dry club? It is so difficult that multiple objects will access this at the same time Method?
Use the existing ones, why repeat inventing the wheel?