eventqueue

In Java, to create and show a new JFrame , I simply do this: public static void main(String[] args) { new MyCustomFrameClass().setVisible(true); } However, I have seen many people doing it like this: public static void main(String[] args) { EventQueue.invokeLater(new Runnable() { public void run() { new MyCustomFrameClass().setVisible(true); } }); } Why? Are there any advantages? The rules governing what needs to be performed on the EDT (I see "EDT" more often used than "Event Queue") have changed during Java's lifetime. And everytime the "rules" changed, Sun advised doing more and more "GUI

In order to debug strange behavior in a Swing-application I'd like to replace the AWT EventQueue with my own implementation. Is this possible? How? Just in case you are interested: the implementation will be a simple wrapper around the normal Eventqueue, doing some logging. the problem I'd like to debug is a TableCellEditor, which works fine in a little demo app, but when put in the real application, stopCellEditing gets called immediately, due to some event. I'd like to get access to the event in order to find out, where it is comming from. EventQueue has a method called push() that will do