Thanks for the help. But I managed to solve this problem by using WM_POROTOCOLS.
Pranay -----Original Message----- From: Mark Vojkovich [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 13, 2001 10:57 AM To: Pranay Kumar Subject: RE: [Xpert]Help: X programming On Tue, 13 Nov 2001, Pranay Kumar wrote: > You mean that window managers actually kill the window and not send a > close event when you press the 'x' on the title bar?? Most window managers do the equivalent of "xkill" on your window. Your connection to the X-server is terminated there on the spot. > Then when is the DestroyWindowEvent called?? I thought it will be called > when the WM closes the window. But I could not get it working? When a window is destroyed you get the event. However, in this case, you're not a client anymore because your connection got terminated. The window and the rest of your resources are cleaned up (destroyed) after it cut you off. See the man page on XSetIOErrorHandler. I think that's the error handler you can install to be informed of such an occurance. Basically Xlib will call that when it finds that it has been cut off. The default handler probably just calls exit(). mark. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
