On 1 March 2010 08:08, Viktor Griph <[email protected]> wrote: > 2009/6/23 Thomas Adam <[email protected]>: >> This isn't a bug in FVWM, and I would imagine awesome have commited >> the sin of assuming all bugs in applications are circumventable in a >> window manager. >> >> The XMMS1 folks didn't like this approach by us, and Audacious clearly >> won't either. ;) >> > > Of course, this "bug" is caused by the use of and EWMH activate > window request before the EWMH move is initiated. And because of the > implementation in fvwm to call a complex function, fvwm will try to > grab the pointer, which won't work since the client still holds a > grab, and thus there will be a timeout (the reported delay) before > fvwm gives up on trying to activate the window. There is a workaround: > to destroy the EWMHActivateWindowFunc.
Sure, but that's not a solution -- that's just a complete hack and affects all applications where a legitimate use of EWMHActivateWindowFunc now isn't possible if you completely destroy it -- you can't even do: + I ThisWindow (Foo) Break for obvious reasons. -- Thomas Adam
