Path: utzoo!attcan!uunet!husc6!rutgers!ucsd!ucbvax!pasteur!cory.Berkeley.EDU!dheller
From: dheller@cory.Berkeley.EDU (Dan Heller)
Newsgroups: comp.windows.x
Subject: Re: Transient Shells and AWM (w/ followup question)
Keywords: override_redirect
Message-ID: <4251@pasteur.Berkeley.Edu>
Date: 4 Jul 88 21:49:54 GMT
References: <350@algol.spp2.UUCP>
Sender: news@pasteur.Berkeley.Edu
Reply-To: dheller@cory.Berkeley.EDU.UUCP (Dan Heller)
Organization: University of California, Berkeley
Lines: 24

In article <350@algol.spp2.UUCP> urban@spp2.UUCP (Mike Urban) writes:
>If I use the Xt toolkit to create a Transient pop-up shell,
>AWM insists on performing "rubber-banding" (calling AskUser),
>because the USPosition and USsize hints are not both set;

>Which of the three participants (awm, Shell(Xt), my application)
>should be changed?
>   Mike Urban
>	...!trwrb!trwspp!spp2!urban 

I fixed this by setting the override_redirect flag to true in the
window attributes structure.  Awm works fine in this context.

However, there is still a problem with destroying this shell.
In the transient shell that I created, I placed a number of widgets,
one of which is a "quit" command button which merely calls
XtDestroyWidget() on the transient shell widget.  The next call to
XtNextEvent tries to do the second phase of the destruction process
and core dumps deep within Xlib ... The only work around I can come
up with is not destroying the widget, but unmapping it instead. This
is bad because I can't free all the memory and resources it consumes.

the question is, what's wrong with destroying a transient shell?
Dan Heller