Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hp-pcd!hpcvlx!keith
From: keith@hpcvlx.cv.hp.com (Keith Taylor)
Newsgroups: comp.windows.x.motif
Subject: Re: Dialog Unmap/'Close' Question and Problem
Message-ID: <110630040@hpcvlx.cv.hp.com>
Date: 1 Apr 91 22:11:36 GMT
References: <1991Mar28.210727.24964@mlb.semi.harris.com>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 31

>What can I do so that the children callbacks get activated as well, even though
>I didn't explicitly 'Close' them? (They need to do some cleaning up too!)

I'm not sure if the unmap callback will get called in this case. I know
if you select for UnmapNotify on your top-level (shell) windows, you 
will get that event (This is Xlib level stuff, though).

(Things can get confused when you have a hierarchy of transient windows
withdrawn by the window manager.)

>What is actually happening when I select the 'Close' option from the
>Window Menu Button?

It depends. If your client has requested the WM_DELETE_WINDOW protocol,
the window manager will send the WM_DELETE_WINDOW message to the client
(and nothing else). This is what you want. Check out
XmAddWmProtocolCallback and VendorShell (XmNdeleteResponse).

>In Motif 1.0, I could double click on the Window Menu Button to activate
>'Close'. Now that I've upgraded to 1.1, this double click doesn't work.
>How can I restore this feature?

This still works for me. On thing that changed was the default time to 
recognize a double-click. Mwm 1.1 dynamically defaults to the value of
multiClickTime which has a shorter default value than mwm's old
doubleClickTime resource.


Keith M. Taylor		keith@cv.hp.com	
Hewlett-Packard
Corvallis, Oregon