Name: vuR10080 Date: 10/28/2000
AWT doesn't properly detect what WM is running. Since AWT uses
information about running WM for some internal heuristic, stale WM
information results in weird effects.
Most stunning example is to start Enlightenment and then exit it and
start, say, sawfish or WindowMaker. Inset calculations in AWT will be
thoroughly ruined (to put it mildly), and since AWT takes insets into
account in size calculations all kinds of weird effect manifest.
Note that I'm not even talking about changing WM *while* and AWT app
is running. A mere fact that Enlightenment *was* ran on the display
sometime in the past is enough to confuse AWT.
. run Enlightenment
. exit Enlightenment (without exiting X session!)
. run, say, sawfish
. start Notepad swing demo
. see Notepad starting as 1-pixel wide window