🚀 go-pugleaf

I see that there is a way to get a window/frame's owned windows, but there is
no way to remove a window from that list.  if that is the case, that implies
that through out the life of a swing application, every window ever
instantiated will never be freed( which of course makes no sense to me ).  I
would imagine that there is a way to release a window from it's owner.  I just
don't know how

Rijk van Haaften wrote:

> On Fri, 26 May 2000 10:17:30 +0100, rocha <rocha@haisystems.com>
> wrote:
>
> . I have an application which instantiates many different windows.  as the
> . application progresses, the performance degrades.  I have traces this
> . problem to the fact that none of the windows are being destroyed until
> . the application terminates and they are holding a lot of memory.  it
> . seems to me that something is still holding a reference to the windows(
> . possible the parent window), but i  don't know how to force there
> . destruction.  does anyone know how to do this?  thanks in advance
> . Ilougino Rocha.
>
> Parts (not all!) of the work can be done with dispose:
>
> java.awt.Window.dispose()
>
> dispose
>
> public void dispose()
>
>      Releases all of the native screen resources used by this Window,
>      its subcomponents, and all of its owned children. That is, the
>      resources for these Components will be destroyed, any memory they
>      consume will be returned to the OS, and they will be
>      marked as undisplayable.
>
>      The Window and its subcomponents can be made displayable again by
>      rebuilding the native resources with a subsequent call
>      to pack or show. The states of the recreated Window and its
>      subcomponents will be identical to the states of these objects at
>      the point where the Window was disposed (not accounting for
>      additional modifcations between those actions).