public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: X11 blinking cursor in text window like 'gvim' - only halts if moved-over another X11-win
Date: Thu, 15 Apr 2021 21:10:47 +0200	[thread overview]
Message-ID: <87sg3rcqiw.fsf@Rainer.invalid> (raw)
In-Reply-To: <1809506730.20210408141940@yandex.ru> (Andrey Repin's message of "Thu, 8 Apr 2021 14:19:40 +0300")

Andrey Repin writes:
>> Windows never had "focus follows mouse" in any version I can remember.
>
> It has it in every version starting Windows 95/NT4.

The last time I tried it it didn't quite work, though.  Specifically it
does "focus strictly follows mouse" and it had problems with raising
unwanted windows in the past.  Again AFAIR…

> @Linda: try http://joelpurra.com/Projects/X-Mouse_Controls/

So I've tried it again… it works better than I remembered.  The ability
of typing into windows that are partially overlapped by another one
probably means I will keep it enabled despite the other problems, but
I'm still sitting on the fence about that.  There are still (less)
problems of the sort that I've had before, but I still see random
Windows getting auto-raised (and briefly taking then losing focus) with
the mouse not even near them (often it's actually on the other screen)
and some applications still needing a click to activate keyboard input
or input to the correct place.  Also some types of keyboard-activated
input fields do not get focus when they open because they get created
away from the mouse pointer, so while formerly they'd be ready to get
input as soon as they pop up, you now have to move the mouse there,
which kind of defeats the purpose.  Also I'd really like a lazy focus
follow that doesn't remove the focus as long as the mouse pointer
doesn't enter another window, but apparently that can't be set up
either.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

  reply	other threads:[~2021-04-15 19:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  0:27 L A Walsh
2021-04-07 18:46 ` Achim Gratz
2021-04-08  8:52   ` L A Walsh
2021-04-08  9:52   ` Lemke, Michael  SF/HZA-ZIC2
2021-04-08 11:19   ` Andrey Repin
2021-04-15 19:10     ` Achim Gratz [this message]
2021-06-16 17:41     ` L A Walsh
2021-04-09 14:41 ` Jon Turney
2021-04-09 15:12   ` Thomas Wolff
2021-04-10 21:40     ` L A Walsh
2021-04-11 14:14     ` Jon Turney
2021-04-10 19:14   ` L A Walsh
2021-04-10 21:37     ` L A Walsh
2021-04-11 14:33       ` Jon Turney
2021-04-11 14:53         ` L A Walsh

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=87sg3rcqiw.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).