🚀 go-pugleaf

Sorry, I keep forgetting to bring home a code snippit.

After I opened my big mouth, I realized mine is only a way to make the thread modal.  It pauses the thread calling setVisible(true)
or show() putting it into a thread wait().  Then an action event of some kind within the window will do a notify() to rekindle the
sleeping thread.  That's only part of the modal behavior of a Dialog.

It doesn't make the parent window unavailable or disabled, nor does it force the pseudo dialog window to come to the front when any
of the parent hierarchy is selected.

I think this can be done by registering a FocusListener with each of the parent components and calling toFront if focusGained() is
invoked while the modal window is visible.

If you still need more, I'll try to put something like this together as an example for you.
"Torsten Welches" <torsten.welches@who.cares.netcologne.de> wrote in message news:3a669326$1_2@dnews...
>
> Rick,
>
> interesting! Would you mind to post some info/snippets about it?
> I guess you mean something like reimplementing Dialog -
> including your own ui-event pump and so on.
> I always thought this still wasn't possible without a true modal
> (native/peer) window component.
>
> Torsten
>
> "Rick Ingham" <rdingham@home.com> wrote:
> >I did this once using thread synchronization and an overridden show()/hide() that called wait()/notify().
>