From: martin rudalics <rudalics@gmx.at>
To: Markus Triska <triska@metalevel.at>, 52666@debbugs.gnu.org
Subject: bug#52666: 27.0.50; Unexpected mode line flickering when creating frames
Date: Mon, 20 Dec 2021 10:18:48 +0100 [thread overview]
Message-ID: <0c04099a-02c7-6bf0-b2cf-492327a1582e@gmx.at> (raw)
In-Reply-To: <m2r1a8mimq.fsf@metalevel.at>
> to reproduce this issue, please put the following form in a new file
> flicker.el:
>
> (while t
> (let ((f (make-frame `((parent-frame . ,(selected-frame))
> (left . 200)
> (top . 200)))))
> (set-frame-width f 200 nil t)
> (set-frame-height f 200 nil t)
> (sit-for 0.3)
> (delete-frame f)))
>
> and then invoke Emacs with:
>
> $ emacs -Q -l flicker.el
>
> The form repeatedly creates and destroys a child frame, offset 200
> pixels both horizontally and vertically from the top left corner of the
> frame.
>
> Unexpectedly, the mode line flickers in many (though apparently not all)
> iterations, starting at 200 pixels horizontally from the left, even
> though the frame does not overlap the mode line in any way.
>
> Ideally, the creation of the frame should not have any visible effect on
> the mode line.
I can reproduce the flickering with a GTK build where the child frame
never appears at all. I cannot reproduce it with a Lucid build where
the child frame appears shortly and gets deleted as expected. In either
case the mode line is redrawn because it changes from active to inactive
and back.
> Could the pleasant double buffering feature I have read about help to
> remove this flickering when creating child frames? Please let me know if
> you can reproduce the issue or need any further information. I can
> reproduce the flickering both on OSX and on Debian.
The (sit-for 0.3) might conflict with 'x-wait-for-event-timeout' so
playing around with the latter could help. BTW is yours really a Lucid
build on a Mac?
martin
next prev parent reply other threads:[~2021-12-20 9:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 20:42 bug#52666: 27.0.50; Unexpected mode line flickering when creating frames Markus Triska
2021-12-20 9:18 ` martin rudalics [this message]
2021-12-20 15:11 ` Eli Zaretskii
2021-12-20 17:21 ` martin rudalics
2021-12-20 18:23 ` Markus Triska
2021-12-20 18:30 ` martin rudalics
2021-12-20 18:41 ` Markus Triska
2021-12-21 10:32 ` martin rudalics
2021-12-21 20:44 ` Markus Triska
2021-12-22 9:22 ` martin rudalics
2021-12-22 13:37 ` Eli Zaretskii
2021-12-22 16:33 ` Markus Triska
2021-12-23 14:46 ` martin rudalics
2021-12-23 16:23 ` Markus Triska
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=0c04099a-02c7-6bf0-b2cf-492327a1582e@gmx.at \
--to=rudalics@gmx.at \
--cc=52666@debbugs.gnu.org \
--cc=triska@metalevel.at \
/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).