unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Flicker on MS Windows
Date: Mon, 07 Mar 2022 22:04:46 +0800	[thread overview]
Message-ID: <87a6e1n9j5.fsf@yahoo.com> (raw)
In-Reply-To: <83v8wqexox.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 07 Mar 2022 14:47:42 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Then I'm afraid I cannot reproduce this.  I tried Emacs 27 on 2
> different versions of Windows 10, and I don't see any abnormal
> flickering when I lean on C-v.  The menu bar does flicker once in a
> few seconds (and that is expected, given how eagerly we update our
> menus)), but by that time Emacs scrolled many window-fulls.

Hmm, that's weird.

> Are you trying this with an optimized build or an unoptimized build?
> An unoptimized build cannot keep up with the auto-repeat rate of the
> keyboard, so the first scroll through the file could cause Emacs to
> become stuck until you release the key.  But once you scroll the file
> once (i.e. it is all fontified), even an unoptimized build behaves
> reasonably, and I see no particular flickering, at least not on the
> menu bar.

It's an optimized build, with "-O2 -g3".

> I certainly don't see any artifacts like left-over text -- that smells
> like some "optimization" of your video driver.  Try disabling any
> advanced features of the display adapter you have there.

I meant to say that I guessed that w32_scroll_run is somehow involved by
commenting out w32_scroll_run and observing that old text was left-over
in places which would previously not flicker during scrolling.  (Because
copying the area that can be scrolled is faster than displaying the rest
of the screen contents, so the system displays the scrolled contents
before the rest can be drawn.)

> Ah, you mean the call to w32_scroll_run in dispnew.c...  Does setting
> w32-use-visible-system-caret non-nil help in any way?

It makes it flicker less, but the flicker is still noticable.

BTW, here's another way to reproduce some severe flicker on MS Windows:
just type "M-: (run-hooks 'xref-after-jump-hook) RET", and the tool bar
buttons, cursor and text start to flicker severely.  The tool bar
buttons flicker in a peculiar way: the background is displayed, but the
image itself flickers with interleaved bands of black.

It's also not affected by the setting of w32-use-visible-system-caret.

Thanks.



  reply	other threads:[~2022-03-07 14:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87o82jpeee.fsf.ref@yahoo.com>
2022-03-06 10:24 ` Flicker on MS Windows Po Lu
2022-03-06 11:13   ` Eli Zaretskii
2022-03-06 11:27     ` Po Lu
2022-03-06 17:46       ` Eli Zaretskii
2022-03-07  0:40         ` Po Lu
2022-03-07 12:47           ` Eli Zaretskii
2022-03-07 14:04             ` Po Lu [this message]
2022-03-07 14:21               ` Eli Zaretskii
2022-03-07 14:28                 ` Eli Zaretskii
2022-03-08  0:25                   ` Po Lu
2022-03-07 17:35                 ` Eli Zaretskii
2022-03-08  0:26                   ` Po Lu
2022-03-08  3:28                     ` Eli Zaretskii
2022-03-06 16:59   ` Óscar Fuentes
2022-03-06 17:05     ` Eli Zaretskii
2022-03-06 17:10       ` Óscar Fuentes
2022-03-06 17:19         ` Eli Zaretskii
2022-03-06 18:09           ` Óscar Fuentes
2022-03-07  0:38             ` Po Lu
2022-03-07  0:37         ` Po Lu

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87a6e1n9j5.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).