[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [External] : Re: master 127ab231be 1/2: Attempt to clarify Input Foc
|
From: |
Eli Zaretskii |
|
Subject: |
Re: [External] : Re: master 127ab231be 1/2: Attempt to clarify Input Focus documentation |
|
Date: |
Thu, 22 Sep 2022 19:24:51 +0300 |
> From: chad <yandros@gmail.com>
> Date: Thu, 22 Sep 2022 12:16:59 -0400
> Cc: Drew Adams <drew.adams@oracle.com>, Eli Zaretskii <eliz@gnu.org>,
> "gregory@heytings.org" <gregory@heytings.org>, "larsi@gnus.org"
> <larsi@gnus.org>, Po Lu <luangruo@yahoo.com>
>
> Back in the day, X programs knew how to distinguish between windows
> appearing/disappearing on their own
> and the window under the mouse being changed by the window manager, and focus
> could be managed
> appropriately. WM's of the time also had (configurable) thresholds for
> whether such accidental movements
> would trigger focus changes or not.
Ironically, the MS-Windows implementation of this feature also has
such thresholds. Like how much time should the mouse hover over a
window before that window gets focus.