-- Jules Alberts ---------------------------------------------------------------------- On Wed, 2003-07-23 at 06:31, Dominik Vogt wrote: > On Wed, Jul 23, 2003 at 11:55:22AM +0200, Jules Alberts wrote: > > Op 23 Jul 2003 (10:59), schreef Dominik Vogt <fvwm_at_fvwm.org>: > > <snip> > > > > And it does, thanks! Another question (also new behaviour since the > > > > upgrade). When I try to move gkrellm (2.1.12) it stays where it is > > > > until I release the mousebutton, then it pops at the position of the > > > > mousecursor. Any ideas? Thanks! > > > > > > Do you mean by clicking on the internal title of the gkrellm > > > window? > > > > Actually it's the hostname of my box inside gkrellm, and gkrellm is > > "NoTitle'd". > > That's what I meant. > > > It does something else that's weird. If I click hostname and keep mouse > > button 1 pressed, after about 1.5 seconds the PC speaker beeps and I > > can move gkrellm normally. > > Gkrellm is probably trying to grap control of the mouse pointer > but some other application has already grabbed it - most likely > fvwm itself. Do you have any mouse bindings on the 'W' indow > context? A la > > mouse 1 w n ... > > If fvwm has grabbed the pointer, that is because you somehow told > it to do so. > > > If I click hostname and move the > > mousepointer (still keeping mouse button one pressed), after the same > > time, gkrellm pops to the new cursorposition. > > > > Other apps don't do this (not even xmms). > > > > > I don't know, it works for me. It's probably a bug in > > > gkrellm. > > > > Could be, but before I upgraded fvwm it worked as expected and I didn't > > change anything gkrellmish. > > > > I tried changing some of gkrellm internal properties (sticky state > > etc.) but that doesn't change anything. Strange... > > Bye > > Dominik ^_^ ^_^ Since I could reproduce this, I decided to track it down... fvwm is indeed trying to grab the pointer and failing [XBell() at functions.c:992 in execute_complex_function], however, it's not because of anything Jules has done... In ConfigFvwmDefaults, an EWMHActivateWindowFunc function is defined--whenever gkrellm is clicked on to be moved (I think GTK2 is what's actually causing this to happen), EWMHActivateWindowFunc is called, causing this problem. -- Ben Winslow <rain_at_bluecherry.net> ---------------------------------------------------------------------- -- 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 majordomo_at_fvwm.org. To report problems, send mail to fvwm-owner_at_fvwm.org.Received on Mon Jul 28 2003 - 01:52:02 BST
This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:55 BST