On Wed, 21 Sep 2005, Dominik Vogt wrote:
On Wed, Sep 21, 2005 at 12:05:15AM +0200, Viktor Griph wrote:
2. What is the reason for windows dropped by button 1 to not fall over to
button release, as windows dropped by button three. I know that not doing
so allows to keep moving the window until you release the button, but why
different behaviour for different buttons?
Can you post a config and some instructions to demonstrate the
problen, please?
It's not really a configuration problem, but a code related one. With the
current code placing with button three imedeatly finishes the placement
(i.e fallthroug to button release in the button event, but placing with
button 1 allows the window to be moved until the button is released. I
think it's strange to have two different types of bavaviour depending on
what button you place the window with. Is there any reason for this, if
not, which is the desired functionality?
Yes, there is a reason. I can't fully remember how all of this
works, but look for the work "PlacedByButton3" in the man page.
It occurs in several places.
There is no where in the man paer an explaination why (or even statement
that it is that way) when placing a window, moved without holding a mouse
button, the window may be kept moving until the button is released if
pressing (and holding) button one, compared to the effect that the window
locks at the position it were when the button was pressed if pressing
button three.
I myself find the way button 3 woks now the nicest, since I then can place
the window where I wan't it without risk of dragging it away upon a sudden
movement just after release. If you really want button one to keep
dragging the window until the button is released I can hardcode that into
the placemnt changes I'm working on, but I still see no real reason to do
it.
/Viktor
