Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!alfalfa.com!nazgul
From: nazgul@alfalfa.com (Kee Hinckley)
Newsgroups: comp.windows.x.motif
Subject: Re: Dialog Unmap/'Close' Question and Problem
Message-ID: <910330104156.4613@sun>
Date: 30 Mar 91 15:41:56 GMT
References: <1991Mar28.210727.24964@mlb.semi.harris.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 26

> The problem is when I 'Close' a dialog that has 1 or more children dialogs,
> (i.e. "dialog1" or "dialog2"); the UnmapCallback *DOES NOT GET CALLED* for
> the children dialogs, even though they disappear. For example, 'Close'
> dialog2, then dialog2 and dialog3 disappear, and dialog2 UnmapCallback gets 
> called but dialog3 UnmapCallback does *NOT*.
> I tried the DestroyCallback, but that doesn't seem to get activated for the
> children either.

Beware.  I recently discovered (and this is probably related indirectly to
your problem) that the feature of closing a parent window and having its
child windows go away to is specific to Mwm.  In particular Olwm does not
do this - which means that it's going to be your responsibility to clean
up the child dialogs.  This *might* be fixable by putting them in the same
group or hand setting transient_for - I'm not sure, I haven't tried yet.
If anyone has any advice I'd appreciate it.

(Note that the same problem exists on iconicizing windows too.  Olwm is a
pretty stupid window manager.)

Alfalfa Software, Inc.          |       Poste:  The EMail for Unix
nazgul@alfalfa.com              |       Send Anything... Anywhere
617/646-7703 (voice/fax)        |       info@alfalfa.com

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.