java - Is it safe to construct Swing/AWT widgets NOT on the Event Dispatch Thread? -

I am feeling and feeling in my application and check it for internal ADT (Event Dispatch Thread) routine. At the same time, UI refuses to build classrooms outside the EDT. I've done lots of swing / AWT and I have a lot of rules about EDT. I use SwingWorker, SwingUtilties.invokeLater to modify the components. I always though that component can be protected outside the EDT, but realize and

I ask that to include a specially "fleshy" window, include several widgets, states, and resources (too many icons). First, I had built a window on the background pattern of swingwalker and appeared in the window in the methodology. There was never a problem. On switching to subStance, the internal ADT check bites me.

I am able to rifroid code to get around this. I can build on ADT which is not a good solution because the entire application will be blocked. I can also reflection and can do my best to load all the extra resources outside of the EDT.

Wrap it ... What build

realized once in the EDT Had to go.

The new rule now reads:

To avoid the possibility of deadlock, you should be careful that the Swing components and models have been created , Modified and asked only for the event-dispatch thread. / P>

My blog post provides more details, including links to other related articles, note that all the official Sun has been rewritten and is very strict about it.

Historically, this was possibly an increasing availability in the form of a multi-core desktop desktop desktop, which became more apparent on the Regulatory Client Stack, and due to the strict ETT guidelines, Many can be prevented from the beginning.