Name: el35337 Date: 09/21/98
There are occasions in an application where it is just plain easier coding to create a secondary event thread to handle the AWT events while the main event thread is blocked. This is evidenced by the way Dialog creates its own instance of the DispatchEventThread.
The problem is that the DispatchEventThread class is package-protected which means I cannot access it from my application AND the SwingUtilities.isEventDispatchThread() method which assumes any event thread is derived from the original DispatchEventThread.
It would also be nice to be able to replace the default thread with my own so I can do some additional processing before and after each event is dispatched (for logging purposes).
(Review ID: 38279)