On Thu, Nov 06, 2003 at 12:14:18PM -0500, Ben Winslow wrote: > On Thu, 2003-11-06 at 03:33, Dominik Vogt wrote: > > On Wed, Nov 05, 2003 at 11:17:21PM -0500, Ryan Daly wrote: > > > I'm noticing something strange with 2.5.8 and gkrellm (2.1.21). > > > > > > I click in the top area to move the window and go to move the mouse, but > > > the window stays put. After about 2 or 3 seconds, I hear a beep and the > > > window all of a sudden appears under my pointer ready for me to place it > > > anywhere. > > > > > > If I use my hotkey to move it, I don't get the delay. > > > > > > Is this a bug or maybe a compile option I missed? > > > > gkrellm and fvwm are competing for a grab on the pointer. The > > beep indicates that fvwm has finally given up. Make sure you don > > not have any mouse bindings like > > > > Mouse 1 w ... Function ... > > > > in your fvwm config. > > n.b. This won't matter--Not only is a complex function needed to > properly move a window by clicking and dragging, but > EWMHActivateWindowFunc is called when you try to start dragging the > gkrellm window.
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. > The only way I know of to get work around all this is to either call > Move in a context that it doesn't have a window (i.e. the cursor changes > and then you click and drag someplace on the gkrellm window), or to have > a move binding that captures the mouse before gkrellm has a chance (e.g. > I have mod3-mouse1 bound to a complex function that immediately runs > move.) (The latter appears to be one thing the original poster > mentioned as working.) Ciao Dominik ^_^ ^_^ -- 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]
