Dan Espen <[EMAIL PROTECTED]> writes: > > I've been trying to debug this, but I'm pretty much stuck. > I've been working off the workers list, but in this case, > I'm copying the list since I'm out of ideas, and I see something > pretty strange.
Further developments: I find I can't create the problem in an Xnest window, but I can on :0. Thats seems very consistent. Using prints, I see that HandleUnmapNotify calls destroy_window leading to the window the main window being destroyed. HandleUnmapNotify doesn't seem to get called inside Xnest. I think what I need to do is print more of the information about the event. Right now, I have no idea how to do that, or what to look for, so I have to do more research. Of course, hints would be appreciated. Doesn't an Unmap event indicate the application has unmapped itself? Looking at the logic in HandleUnmapNotify, it looks like its not that simple. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
