Re: [qvwm-devel] qvwm and numlock focus problem

[Mitch D. <mj...@al...>]

Benjam=EDn Albi=F1ana P=E9rez wrote:
>  Cuando: mar, 21 de oct de 2003, a las 08:28:43 +0300
>  Quien: ali...@tt...
>  Que: [qvwm-devel] qvwm and numlock focus problem
>=20
>=20
>>i work on qvwm focus problem on if numlock key activated.
>>what do you think this problem
>=20
> =20
>    I don't like (and so, don't use) the click to focus feature, as it
>    only works by clicking on titlebar, and very often I work with
>    aterm with no border, no title, no scrollbar, nothing.

Hi Benjam=EDn,

I have talked with Ali.  Finally, I understand what he's saying! :-)

Assume that you have ClickToFocus set to True (which I don't, I like
focus-follows-mouse), and that you have two windows (maybe xterms)
open.

You already know you can change the focus between one and the other
by clicking the bar on the top each window.  But in addition to that,
NumLock controls whether you can also change focus by clicking in the
client area of the other window.  NumLock off, you can change focus
by clicking inside the other window.  NumLock on, you can't.

 >    I have tested here, with a couple of xterms and numlock key
 >    activated (defaults here), and seems not to be any problem.

Try NumLock key off.  You can change focus even if there's no
titlebar!  And that's the behaviour that you're looking for, when
you have windows without a titlebar.  (xmms is another one...)

Related to this is what happens in when ClickToFocus=3DFalse mode.
You can stop qvwm from taking focus away when your mouse leaves
a window by holding down the shift key.  This is something a user
might want to choose to do temporarily, and it doesn't stop the
shift key from working as usual.

But the NumLock thing is different.  First, whichever way the user
wants it, they are unlikely to want to change the behaviour temporarily.
Also, it prevents the proper use of NumLock for numbers, cursor, etc etc.

So I agree with Ali: The NumLock thing may have been intended as a
feature, but to me it seems to be a bug.

I suggest a new command in the .qvwmrc file, which specifies the
behaviour.  And this behaviour is off by default in the standard
qvwmrc files.  And NumLock will no longer change it when you're
running.

Any thoughts?

Mitch.