From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from Ishtar.sc.tlinx.org (ishtar.tlinx.org [173.164.175.65]) by sourceware.org (Postfix) with ESMTPS id 562AD3857C63 for ; Sat, 10 Apr 2021 21:37:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 562AD3857C63 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tlinx.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cygwin@tlinx.org Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id 13ALbX2s016779; Sat, 10 Apr 2021 14:37:35 -0700 Message-ID: <60721A9B.1000605@tlinx.org> Date: Sat, 10 Apr 2021 14:37:31 -0700 From: L A Walsh User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Jon Turney CC: The Cygwin Mailing List Subject: Re: X11 blinking cursor in text window like 'gvim' - only halts if moved-over another X11-win References: <606CFC89.6030700@tlinx.org> <3a23e83c-670b-c599-b77b-18074dadf42e@dronecode.org.uk> <6071F92E.5050802@tlinx.org> In-Reply-To: <6071F92E.5050802@tlinx.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Apr 2021 21:37:37 -0000 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 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?