From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: kbrown@cornell.edu, emacs-devel@gnu.org
Subject: Re: MS Windows double buffering
Date: Sat, 30 Apr 2022 17:55:32 +0800 [thread overview]
Message-ID: <87ee1euc8b.fsf@yahoo.com> (raw)
In-Reply-To: <83v8ur7x8p.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Apr 2022 12:10:14 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Emacs is being tested on X much more than on MS-Windows, and people
> who use it on X tend to be more knowledgeable about the technical
> issues than a typical user of Emacs on Windows. Moreover, the level
> of expertise we have on our team about Windows-specific GUI aspects is
> significantly lower than in the X case.
>
> So having such a debugging device for significant changes in display
> code is beneficial.
Thanks for clarifying.
> So you are saying this code didn't work correctly before? Or am I
> misunderstanding something?
No, it was a misunderstanding on my part. Sorry for the noise.
> This still flickers considerably here, albeit with a significantly
> lower frequency.
What if you comment out these lines in w32term.c?
if (f && !w32_disable_double_buffering
&& FRAME_OUTPUT_DATA (f)->paint_buffer_dirty
&& !f->garbaged && ignore_dirty_back_buffer)
w32_show_back_buffer (f);
> What other test cases in the discussions would you recommend to try?
(run-hooks 'xref-after-jump-hook)
for example, which causes considerable flickering without double
buffering, but none at all when double buffering is enabled.
next prev parent reply other threads:[~2022-04-30 9:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877d791thh.fsf.ref@yahoo.com>
2022-04-28 8:51 ` MS Windows double buffering Po Lu
2022-04-28 9:42 ` Eli Zaretskii
2022-04-28 12:45 ` Po Lu
2022-04-29 3:36 ` Po Lu
2022-04-30 5:41 ` Po Lu
2022-04-30 6:50 ` Eli Zaretskii
2022-04-30 7:46 ` Po Lu
2022-04-30 9:10 ` Eli Zaretskii
2022-04-30 9:55 ` Po Lu [this message]
2022-04-30 10:23 ` Eli Zaretskii
2022-04-30 10:33 ` Po Lu
2022-04-30 10:55 ` Eli Zaretskii
2022-04-30 11:01 ` Po Lu
2022-04-30 11:32 ` Eli Zaretskii
2022-04-30 11:54 ` Po Lu
2022-05-03 8:23 ` Robert Pluim
2022-05-03 8:43 ` Po Lu
2022-04-30 17:34 ` Ken Brown
2022-04-30 18:25 ` Eli Zaretskii
2022-05-01 0:35 ` Po Lu
2022-05-01 16:00 ` Arash Esbati
2022-05-01 16:07 ` Eli Zaretskii
2022-05-01 16:11 ` Arash Esbati
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=87ee1euc8b.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.