public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Updated: xorg-server-1.19.3-1
Date: Sat, 22 Apr 2017 17:10:00 -0000	[thread overview]
Message-ID: <CAK-n8j5jCKnS0yaaYXNA9n+eHJrw7J_TCvuQrkb89Kn4aqdFMg@mail.gmail.com> (raw)
In-Reply-To: <CAK-n8j76CWLCrCAyCB6Fbm0TQJAt8LAc6nFk6wHR-jt2PjxuAg@mail.gmail.com>

> * If I'm in an X Emacs window, then click back in my X term, the focus
> is still with the X Emacs window.

I misspoke, and left out an important detail:

If the windows do *not* overlap, then there appears to be no problem.

If the XTerm window is behind the XEmacs window while I'm editing,
then I move the mouse pointer back into the Xterm, neither window has
focus.  I can move the mouse pointer back into the XEmacs window to
get focus there, but I can never get focus back to the Xterm.

Furthermore, the particular Windows setting I'm using for mouse
activation is in the "Ease of Access Center", under "Make the mouse
easier to use".  I have "Activate a window by hovering over it with
the mouse" checked.  In addition, I'm using a Windows registry hack to
simply give the window focus without making it active, i.e. moving it
to the top:

http://winaero.com/blog/turn-on-xmouse-active-window-tracking-focus-follows-mouse-pointer-feature-in-windows-8-1-windows-8-and-windows-7/

- Jim

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-04-21 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <aff8f9a9-994b-afe8-e28f-e7b80d218389@dronecode.org.uk>
2017-04-22 15:50 ` Jim Reisert AD1C
2017-04-22 17:10   ` Jim Reisert AD1C [this message]
2017-04-23 22:45     ` Jon Turney

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

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

  git send-email \
    --in-reply-to=CAK-n8j5jCKnS0yaaYXNA9n+eHJrw7J_TCvuQrkb89Kn4aqdFMg@mail.gmail.com \
    --to=jjreisert@alum.mit.edu \
    --cc=cygwin@cygwin.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).