On Tue, Jul 02, 2002 at 09:27:21AM +0200, Philippe Naudin wrote: > On Sat, 29 Jun 2002 21:53:01 +0200 > Dominik Vogt <[EMAIL PROTECTED]> wrote: > > > On Tue, Jun 25, 2002 at 11:49:33AM +0200, Philippe Naudin wrote: > > > [snip] > > > the option ClickToFocusPassesClickOff works fine when I click an > > > unfocused aterm or rxvt, but not when I click and move the mouse before > > > releasing the button (the client is focused _and_ a selection is made in > > > it). > > > [snip] > > > > There is little we can do about that. It's not the click that > > gets passed to the window - insofar fvwm works correctly. The > > problem is that rxvt and aterm request pointer motion events with > > any button held down. Fvwm releases the grab of the pointer after > > the click is processed and further mouse events are processed by > > the application. It does not happen with xterm because xterm > > requires to receive the click. > > > > Bye > > Hello Dominik, > > aterm was working fine with fvwm-2.3.20. "Unfortunately" ;) there as > been many improvements in version 2.4 and it would be a pity to switch > back. > OTOH, I really like the look of aterm or rxvt ... Would it be possible > to change the behaviour of FVWM so it grabs the pointer until the button > release ?
Yes, that's what the old code up to 2.3.23 was doing. It's not very nice to block the mouse completely in this case, but it seems necessary here. I have restored the old way for this special case. Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
