[604] in Athena User Interface
Try this one on for size.
daemon@ATHENA.MIT.EDU (t. belton)
Thu Jan 11 13:38:41 2001
Date: Thu, 11 Jan 2001 13:38:38 -0500 (EST)
From: "t. belton" <tbelton@MIT.EDU>
To: <aui@mit.edu>
Message-ID: <Pine.GSO.4.30L.0101111325300.12537-100000@iphigenia.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Today I logged on normally in the morning, using the AUI environment, as I
have done for weeks. I know everything was working right (or as well as it
ever does) because I gave a small AUI demo to someone. One of the features
I showed them was how, by clicking on the name of a running window down in
the panel bar, you can easily toggle the window between visible and
invisible.
Logged out, did other things, went back to my desk, logged in, decided I
was tired of some settings in .startup.X that were now obsolete. Changed
my .startup.X from
xsetroot -solid black &
xclock -digital -geometry +950+830 &
xhost kansas.mit.edu
box
to
xsetroot -solid black &
# xclock -digital -geometry +950+830 &
# xhost kansas.mit.edu
box
because panel has a built-in clock and I no longer need to work on kansas.
('box' is an alias which starts an xterm window of a particular size and
name)
Logged out, logged back in.
On this login, panel was acting weird:
1. There were two indicators of open windows in panel which were nowhere
to be seen onscreen. They were both labelled 'panel.' Clicking on them did
nothing.
2. Clicking on the name for an open window in panel made not just the
window, but also its label in panel disappear for good. Later lock file
problems made me realize that the apps were still running, but with no way
to see them or get to them.
3. The windows were being placed strangely onscreen when opened; for
example, the terminal window created when I run 'pine' is usually not
placed so that it overlaps the panel bar; now it did.
After losing several windows and pondering this for a while, I shrugged,
restored my .startup.X to its previous state just for jollies, logged out,
and logged back in.
All three problems had magically vanished.
I will give a cookie to anyone who has a decent guess why such a trifling
change in .startup.X could possibly affect panel behavior in such big
ways.
-Todd
