myoung@ingr.UUCP (Mark Young) (03/15/88)
Greetings.
We imagine this question is going to get a few laughs, but we're
secure individuals, so we'll ask anyway.
Let's suppose, for example, that you are running Uwm. You start
a graphics intensive X client, and then decide that you'd really like to
dedicate some of the display speed to an xterm so you can get some real
work done.
The Question is:
How do you suggest that we get that client's window to:
Chuck the wuckie,
Give up the ghost,
Kick the bucket...
Get Unmapped or Destroyed.
We'd always kind of guessed that this would be a function of the
window manager. This way you'd have a consistent interface to getting rid
of client windows. I wouldn't consider an acceptable response to the
question to be "well, that functionality should be built into the client."
We wrote an application that allowed you to select a window on the
screen to be destroyed, but most clients didn't deal with this too well :-).
I remember discussion at the X conference about window manager
specifications. Is there a guide that exists defining what are and are not
the server's responsibilities in situations such as this. it seems fairly
fundamental.
...myoung & dwiley
aka. Mark A. Young &
Dave R. Wiley
Flames ---------------------------------------------------------> /dev/null
ingr!myoung!myoung@uunet.uu.net | mark allan young | where
{uunet,ihnp4}!ingr!myoung!myoung | intergraph corp, cr1105 | do I
xxxxx | one madison industrial pk | put the
xxxxxx "the xwave of the future" | huntsville, al 35807 | usual
xxxxxxxxxxxx | (205) 772-6094 | disclaimer