DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 00C523857816
Subject: Re: X11 blinking cursor in text window like 'gvim' - only halts if
 moved-over another X11-win
To: L A Walsh <cygwin@tlinx.org>, The Cygwin Mailing List <cygwin@cygwin.com>
References: <606CFC89.6030700@tlinx.org>
 <3a23e83c-670b-c599-b77b-18074dadf42e@dronecode.org.uk>
 <6071F92E.5050802@tlinx.org> <60721A9B.1000605@tlinx.org>
From: Jon Turney <jon.turney@dronecode.org.uk>
Message-ID: <0d803d41-42b6-4725-b1c8-3e01486907fb@dronecode.org.uk>
Date: Sun, 11 Apr 2021 15:33:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.9.1
MIME-Version: 1.0
In-Reply-To: <60721A9B.1000605@tlinx.org>
Content-Language: en-GB
Precedence: list
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: cygwin-bounces@cygwin.com
Sender: "Cygwin" <cygwin-bounces@cygwin.com>
Content-Transfer-Encoding: 8bit

On 10/04/2021 22:37, L A Walsh wrote:
> On 2021/04/10 12:14, L A Walsh wrote:
>> On 2021/04/09 07:41, Jon Turney wrote:
>>> I think so, yes.
>> ===
>>
>>     That's unfortunate.  Well, I wasn't sure if it was new
>> or old. At least its not some new problem.  Sigh.
>>
>>     Thanks for the backstory.
>>> [1] https://sourceware.org/legacy-ml/cygwin/2017-04/msg00168.html
>>> [2] https://sourceware.org/legacy-ml/cygwin/2017-04/msg00278.html
>>> [3] https://sourceware.org/pipermail/cygwin/2017-May/232564.html
> ---
>    I don't know if this was tried, but the only way to really do
> it would be along the lines of detecting when windows had grabbed
> control via its time -- for cygwin to use a timer to detect when it
> lost control.  Ex. in cygwin's blink routine, it would need to check

There is no 'cygwin blink routine' - this is something that the X client 
(e.g. gvim in your example) is doing, while it believe that it has focus.

> that it still had focus, and if it had lost it for longer than 50-75ms
> (maybe configurable), assume cursor is over a Win-Window...  May not
> be worth the bother, but it might catch the problem?

There's almost certainly no need for such heuristics.  Windows provides 
various notification messages when the focus is moving, it's translating 
those (correctly) into the model that X clients expect that is the problem.
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple