> Sorry, my use of "blocking" was not intended to be technically accurate. > Of course, it has to keep pumping the event loop, which is what makes it > so tricky. Actually, the tricky code seems to be in java.awt.Dialog > where the modal event loop lives.
Right, that's what I would have guessed. But in any case, this sort of behavior would require access to the native event queue, which AWT does not provide (and I'm not sure should be exposed anyway). G
