Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ATHENA.MIT.EDU!wdc
From: wdc@ATHENA.MIT.EDU (Bill Cattey)
Newsgroups: comp.soft-sys.andrew
Subject: Transients update.
Message-ID: <ob9=ISgGG02=0mhtU_@athena.mit.edu>
Date: 23 Oct 90 21:24:46 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 28

Thanks much many, Andy, for telling me to make the transient a child of
the root window, not of the other window.  This has cured the problem of
mouse events I wanted to give to the transient window going to the
parent window.  The bad interaction of old dialogue boxes and my
transients is fixed.

Here, for the benefit of other interested info-andrew readers, are the
revisions to the design of transients:

1.  im_CreateTransient creates a window that is a "transient for another
window".  It's purpose is to create windows located relative to another
window.  Such windows are for things like Palettes where their operation
can happen concurrently with the other window they're associated with.

2. im_CreatePopUp will be written for windows that must operate while
the other window they are associated with is not allowed to receive
input.  Such windows are for dialogue boxes.  This is a transient with
override_redirect set, and it requires fiddling with the im_  main loop
to forward keyboard and button events from the other window to this one.

Open issues:

1. What should the interface be if im_CreatePopUp is not supported?

2. Should there be a compile-time or run-time variable or call that
tells if the window server supports the Transient or PopUp window types.

-wdc