🚀 go-pugleaf

That rings a bell.  I just don't remember how you invoke a new event handler thread and stop it after you want to return.  There's a
technique for doing this, but I don't remember where I saw it.  It may have been in JOptionPane.

"Torsten Welches" <torsten.welches@who.cares.netcologne.de> wrote in message news:3a69c8e9_1@dnews...
> Rick,
>
> the problem with your ModalWindow is that it "waits" the AWT event dispatch
> thread without providing a replacement event pump - that's what Dialog does.
> All gui painting stops after your line:
>   if( visible ) myMutex.wait();
>
> Try putting some components on your parent JFrame and invoke your
> ModalWindow. Now iconify and restore your parent and you will see the
> problem.
>
> Torsten
>
> Rick Ingham schrieb in Nachricht <94av0c$6i95@bornews.inprise.com>...
> >I don't think a Dialog box stops other "processes" or threads other than
> the one making the dialog visible, does it?  I would hope
> >it doesn't stomp on all the other threads.  This could kill background
> processing and network activity creating timeout disconnects
> >and such.
> >
> >I'm curious if anyone else has suggestions on improvements to bring this
> closer to Dialog behavior.
>
>
>