GNU bug report logs - #40278
Flickering in Windows 10 (not double buffered)

Previous Next

Full log

Message #41 received at 40278 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Nicolas Bértolo <nicolasbertolo <at> gmail.com>
Cc: 40278 <at> debbugs.gnu.org, rudalics <at> gmx.at, npostavs <at> gmail.com
Subject: Re: bug#40278: 27.0.90; Flickering in Windows 10
Date: Tue, 31 Mar 2020 18:56:39 +0300

> From: Nicolas Bértolo <nicolasbertolo <at> gmail.com>
> Date: Tue, 31 Mar 2020 12:51:37 -0300
> Cc: Noam Postavsky <npostavs <at> gmail.com>, Eli Zaretskii <eliz <at> gnu.org>, 40278 <at> debbugs.gnu.org
> 
> > I have no idea why this should be related to scrolling.  Does any of
> > these happen with a normal frame put on top of the window you scroll?
> 
> I think it is not possible to input into a frame that is partially hidden (and
> thus not focused) by others in Windows. The mouse wheel does nothing and
> keyboard inputs go to the topmost window.

It's possible, but you need to turn on the "active window tracking"
feature.  There are tiny programs floating around that allow you to do
that.  With that feature turned on, focus follows the mouse, like on X
Window system on Unix.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.