On Wed, May 19, 2010 at 10:00:50AM -0700, Omar Zakaria wrote: > Thanks again for looking at this. I really appreciate it. Let me know if > I can help in any way.
Can you please checkout the CVS version of FVWM and apply the patch attached? See if it "fixes" your problem? -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
Index: fvwm/add_window.c =================================================================== RCS file: /home/cvs/fvwm/fvwm/fvwm/add_window.c,v retrieving revision 1.401 diff -u -p -r1.401 add_window.c --- fvwm/add_window.c 2 Aug 2009 15:04:08 -0000 1.401 +++ fvwm/add_window.c 23 May 2010 18:33:50 -0000 @@ -2378,10 +2378,14 @@ FvwmWindow *AddWindow( } else { - attributes.event_mask = XEVMASK_CLIENTW; + /* TA: Temporarily assign Substructure masks here, and + * consider adding them to XEVMASK_CLIENTW if proven to work. + */ + attributes.event_mask = XEVMASK_CLIENTW | \ + SubstructureRedirectMask | SubstructureNotifyMask; } attributes.do_not_propagate_mask = ButtonPressMask | ButtonReleaseMask; - XChangeWindowAttributes(dpy, FW_W(fw), valuemask, &attributes); + XChangeWindowAttributes(dpy, FW_W_PARENT(fw), valuemask, &attributes); /****** make sure the window is not destroyed when fvwm dies ******/ if (!IS_TEAR_OFF_MENU(fw)) {