unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Menu-bar flickering on Win10
Date: Thu, 03 Nov 2022 13:26:33 +0200	[thread overview]
Message-ID: <83y1ss6zyu.fsf@gnu.org> (raw)
In-Reply-To: <86k04cpb7m.fsf@gnu.org> (message from Arash Esbati on Thu, 03 Nov 2022 11:46:21 +0100)

> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Thu, 03 Nov 2022 11:46:21 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I hoped you would be able to actually step through the code (in
> > Edebug) and tell which part causes the flickering...
> 
> I started doing it and then it occurred to me that corfu is not needed
> to trigger the issue.  It is enough to do 'emacs -Q', 'C-x 5 2' and
> switch between the frames, I did it by clicking with the mouse pointer.

Then I simply cannot reproduce this on my system.

> I'm not familiar with Emacs internals, but does this observation fit to
> Po Lu's message where he said:
> 
>   I think menu bar updates are not double buffered on MS Windows, and as
>   a consequence flickers as Emacs removes the items to update them.
> 
> ?

No.



  reply	other threads:[~2022-11-03 11:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 12:08 Menu-bar flickering on Win10 Arash Esbati
2022-11-02 12:14 ` Po Lu
2022-11-02 13:17 ` Eli Zaretskii
2022-11-02 13:35   ` Arash Esbati
2022-11-02 13:53     ` Eli Zaretskii
2022-11-02 14:07       ` Arash Esbati
2022-11-02 15:11         ` Eli Zaretskii
2022-11-03 10:46           ` Arash Esbati
2022-11-03 11:26             ` Eli Zaretskii [this message]
2022-11-03 11:51               ` Po Lu
2022-11-03 13:55                 ` Arash Esbati
  -- strict thread matches above, loose matches on Subject: below --
2022-11-04 12:51 Johan Myréen
2022-11-04 13:54 ` Eli Zaretskii

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=83y1ss6zyu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arash@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).