[414] in java-interest
awt re-design?
daemon@ATHENA.MIT.EDU (Gregory Zoller - Imonics Developme)
Tue Jun 20 15:06:41 1995
From: Gregory Zoller - Imonics Development <gzoller@imonics.com>
Date: Tue, 20 Jun 1995 14:47:32 -0400
To: java-interest@java.sun.com
I've read bits and pieces about an awt re-write. Does anyone know
if this is a 'major' re-do?
I'm mainly interested in knowing if any redesign or restructuring
will be performed to allow objects to be embedded in other objects,
not unlike the third-party AppPanels utility classes.
There seem to be at least one hierarchy bug in this version of awt.
For example, if I have a button object and call its dispose() method,
Java doesn't seem to remove the button from its Window object's
ChildList. (In effect the button is never removed!) To fix this
problem, I have to create a destroy() method and do something like:
item.parent.children.remove("myButton");
Has anyone else had anything like this occur?
It would be very nice to have a Panel which has a ChildList, such that
when I dispose() the Panel, everything else goes too.
Greg
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
