Comments on: Swing EDT and UIManager Initialization Question http://stuffthathappens.com/blog/2007/10/23/swing-edt-and-uimanager-initialization-question/ Technology and Geek Stuff by Eric Burke Mon, 26 Jul 2010 14:36:32 -0400 http://wordpress.org/?v=2.8.6 hourly 1 By: Paranoid http://stuffthathappens.com/blog/2007/10/23/swing-edt-and-uimanager-initialization-question/comment-page-1/#comment-7616 Paranoid Wed, 19 Mar 2008 14:09:51 +0000 http://stuffthathappens.com/blog/2007/10/23/swing-edt-and-uimanager-initialization-question/#comment-7616 I know this article is very old, but can't stay without replying. As i understand, only operations with Graphics or Graphics2D need to be performed from EDT, because Graphics is not synchronized. Almost all other things, including JTable's repaints (marking of dirty regions for repaint manager) and GUI creation can be done from elsewhere. I know this article is very old, but can’t stay without replying.
As i understand, only operations with Graphics or Graphics2D need to be performed from EDT, because Graphics is not synchronized. Almost all other things, including JTable’s repaints (marking of dirty regions for repaint manager) and GUI creation can be done from elsewhere.

]]> By: Eric Burke http://stuffthathappens.com/blog/2007/10/23/swing-edt-and-uimanager-initialization-question/comment-page-1/#comment-538 Eric Burke Tue, 23 Oct 2007 17:54:01 +0000 http://stuffthathappens.com/blog/2007/10/23/swing-edt-and-uimanager-initialization-question/#comment-538 But if UIManager is not designed for thread safety, isn't there a possibility of memory visibility problems, since we are creating objects in the main thread and then accessing them from the event dispatch thread? Seems like UIManager (and everything it touches) would have to be explicitly synchronized, or use volatile, or some similar mechanism, to ensure visibility across threads. But if UIManager is not designed for thread safety, isn’t there a possibility of memory visibility problems, since we are creating objects in the main thread and then accessing them from the event dispatch thread? Seems like UIManager (and everything it touches) would have to be explicitly synchronized, or use volatile, or some similar mechanism, to ensure visibility across threads.

]]> By: codepope http://stuffthathappens.com/blog/2007/10/23/swing-edt-and-uimanager-initialization-question/comment-page-1/#comment-537 codepope Tue, 23 Oct 2007 16:23:39 +0000 http://stuffthathappens.com/blog/2007/10/23/swing-edt-and-uimanager-initialization-question/#comment-537 From my intuition, there is no issue calling UIManager,setLookAndFeel() at startup; it only alters the default values in the library and doesn't trigger any UI changes as there is at that point no UI to be changed. Now, when you do have a UI, then the UIManager.setLookAndFeel can still be done off the EDT, but SwingUtilities.updateComponentTreeUI(...) to redraw the UI should be on the EDT. Both examples are therefore correct, as they both invoke before there's any UI in existence. From my intuition, there is no issue calling UIManager,setLookAndFeel() at startup; it only alters the default values in the library and doesn’t trigger any UI changes as there is at that point no UI to be changed. Now, when you do have a UI, then the UIManager.setLookAndFeel can still be done off the EDT, but SwingUtilities.updateComponentTreeUI(…) to redraw the UI should be on the EDT.

Both examples are therefore correct, as they both invoke before there’s any UI in existence.

]]>