On Tue, Jul 27, 2010 at 04:55:52PM -0400, Chris Siebenmann wrote:
> I wrote:
> | This doesn't happen for other buttons, eg I also have 'Mouse 1
> | T N Move' and if I use mouse button 1 on window titles they move
> | immediately without waiting for button-up.
>
> I was mistaken about what I had button 1 bound to, which has led me
> to a workaround. If you have the Move in a function it activates
> immediately, as you'd expect:
>
> Mouse 2 IT N MoveFunc
>
> DestroyFunc MoveFunc
> AddToFunc MoveFunc
> + I Move
>
> ('M' instead of 'I' is equivalent; I assume that other options probably
> would cause some variety of the button-up behavior I was seeing on the
> basic Move.)
This is due to the fact that functions *grab the pointer* when they execute,
for obvious reasons. (You don't want some other application subsequently
grabbing the pointer at the point a function is running and having random
actions applied to it, for which that window was not intended to ever
receive).
So, not a bug, or anything to worry about at all.
-- Thomas Adam
--
"It was the cruelest game I've ever played and it's played inside my head."
-- "Hush The Warmth", Gorky's Zygotic Mynci.
