On 07 Nov 2003 14:36:55 +0100, Dominik Vogt wrote: > > On Fri, Nov 07, 2003 at 01:10:43PM +0000, Mikhael Goikhman wrote: > > On 07 Nov 2003 10:28:16 +0100, Dominik Vogt wrote: > > > > > > That sounds somewhat familiar. I think you are right. So the > > > problem can be circumvented by either destroying the corresponding > > > fvwm function: > > > > > > DestroyFunc EWMHActivateWindowFunc > > > > > > (which affects all windows, not just gkrellm). Unfortunately, it > > > is not yet possible to disable certain features of the EWMH spec > > > for individual windows. > > > > Destroying this function would be undesirable for modern applications > > asking the window manager to activate (bring to the user attention) their > > windows. > > > > A better solution would be to introduce Grab command and add "Grab off" > > to EWMHActivateWindowFunc. > > Deja Vu? No, it wouldn't.
I.e. you say fvwm should know better than the user what to do and disallow some legitimate functionality. I hope you have a better solution in mind for this kind of problems regarding fvwm functions. Regards, Mikhael. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
