Currently, when one writes test for AWT/Swing he meets with asynchronousity problems of AWT/Swing. When you show a window on the screen, resize/move it, change its decorations and do some other operations, there is no way to detect the moment when such an operation is complete. Many operations have corresponding event notifications, but not all of them. One of the ways to address this problem could be to have an API that allows to force a system to process all requests, generate all events, and process all events internally in Java. We already have a similar API, Robot.waitForIdle() and Toolkit.sync(), but they don't do all that is necessary.
###@###.### 2005-04-07 14:52:43 GMT