unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: chad <yandros@gmail.com>
Cc: emacs-tangents@gnu.org,  Drew Adams <drew.adams@oracle.com>,
	 Eli Zaretskii <eliz@gnu.org>,
	 "gregory@heytings.org" <gregory@heytings.org>,
	"larsi@gnus.org" <larsi@gnus.org>
Subject: Re: [External] : Re: master 127ab231be 1/2: Attempt to clarify Input Focus documentation
Date: Fri, 23 Sep 2022 08:36:19 +0800	[thread overview]
Message-ID: <87v8pfc4fw.fsf@yahoo.com> (raw)
In-Reply-To: <CAO2hHWYioojnZQ+OdMy4tXp-MVusY3aUCQhuG5Sxf-=xG-1siA@mail.gmail.com> (chad's message of "Thu, 22 Sep 2022 12:16:59 -0400")

chad <yandros@gmail.com> writes:

> 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.

"Appearing" or "disappearing" accidental movements?

The reason it is such a pain to manage is that the focus does not end up
in the toplevel window (with WM_TAKE_FOCUS messages), always follows the
mouse regardless of the value of the input flag in the window manager
hints property, and is delivered in terms of crossing events with the
focus flag set.  A single master device can also have both explicit and
implicit focus at any given time.



      parent reply	other threads:[~2022-09-23  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166368675497.15121.15081377110947098460@vcs2.savannah.gnu.org>
     [not found] ` <20220920151239.61451C00871@vcs2.savannah.gnu.org>
     [not found]   ` <87czbpihyl.fsf@yahoo.com>
     [not found]     ` <2d1b683c2245a1b1035c@heytings.org>
     [not found]       ` <87v8phgfv0.fsf@yahoo.com>
     [not found]         ` <2d1b683c22ba04ac1445@heytings.org>
     [not found]           ` <83h711ueqo.fsf@gnu.org>
     [not found]             ` <87pmfpeyae.fsf@yahoo.com>
     [not found]               ` <83czbovqfs.fsf@gnu.org>
     [not found]                 ` <SJ0PR10MB5488616B68EE40EB97B05E47F34F9@SJ0PR10MB5488.namprd10.prod.outlook.com>
     [not found]                   ` <83r104u1k3.fsf@gnu.org>
     [not found]                     ` <SJ0PR10MB548837BEDE6B0D5856BBED3DF34F9@SJ0PR10MB5488.namprd10.prod.outlook.com>
     [not found]                       ` <83pmfotyo8.fsf@gnu.org>
     [not found]                         ` <SJ0PR10MB54881B39C26E2D30F14EA6FCF34F9@SJ0PR10MB5488.namprd10.prod.outlook.com>
     [not found]                           ` <87sfkkdspw.fsf@yahoo.com>
2022-09-22 16:16                             ` [External] : Re: master 127ab231be 1/2: Attempt to clarify Input Focus documentation chad
2022-09-22 16:24                               ` Eli Zaretskii
2022-09-23  0:36                               ` Po Lu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8pfc4fw.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-tangents@gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.org \
    --cc=yandros@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).