From: martin rudalics <rudalics@gmx.at>
To: "Nicolas Bértolo" <nicolasbertolo@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>
Cc: 40278@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#40278: 27.0.90; Flickering in Windows 10
Date: Wed, 1 Apr 2020 08:36:15 +0200 [thread overview]
Message-ID: <a89961bc-4be2-20d1-7cc1-3f728fb07951@gmx.at> (raw)
In-Reply-To: <CAFnS-OkMFcCR0fx6ybY28-SLZ+qxD=34QwQjQWctDfn1xrM74w@mail.gmail.com>
> Emacs frame partially covered by an Emacs frame: Nothing happens. Mouse input
> does not seem to go anywhere.
Might be that here I'm using yet another program to handle that case.
'mouse-wheel-follow-mouse' should not be involved but please make sure
that it's t.
> Emacs frame partially covered by a Windows explorer window: Emacs scrolls
> normally, that is, in my case there is some flickering. But nothing like what
> happens with a child frame.
From what Noam described the flickering could be due to the tool bar.
What happens when you write
(defun open-test ()
(display-buffer-in-child-frame
(get-buffer-create "test child-frame")
'((child-frame-parameters . ((tool-bar-lines . 0)
(width . 20)
(height . 10)
(top . 200)
(left . 100))))))
instead?
martin
next prev parent reply other threads:[~2020-04-01 6:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 16:11 bug#40278: 27.0.90; Flickering in Windows 10 Nicolas Bertolo
2020-03-29 17:25 ` Eli Zaretskii
2020-03-29 20:28 ` Nicolas Bértolo
2020-03-29 20:58 ` Nicolas Bértolo
2020-03-30 14:06 ` Eli Zaretskii
2020-03-30 16:23 ` Noam Postavsky
2020-03-30 16:40 ` Eli Zaretskii
2020-03-30 17:15 ` Noam Postavsky
2020-03-30 18:29 ` Eli Zaretskii
2020-03-30 19:21 ` Noam Postavsky
2020-03-31 8:48 ` martin rudalics
2020-03-31 15:51 ` Nicolas Bértolo
2020-03-31 15:56 ` Eli Zaretskii
2020-03-31 16:10 ` Nicolas Bértolo
2020-04-01 6:36 ` martin rudalics [this message]
2020-04-01 14:25 ` Noam Postavsky
2020-04-01 20:39 ` Nicolas Bértolo
2022-05-16 11:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=a89961bc-4be2-20d1-7cc1-3f728fb07951@gmx.at \
--to=rudalics@gmx.at \
--cc=40278@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=nicolasbertolo@gmail.com \
--cc=npostavs@gmail.com \
/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).