From: Alan Third <alan@idiocy.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: konrad.podczeck@univie.ac.at, 42406@debbugs.gnu.org
Subject: bug#42406: Mouse-wheel scrolling can be flickering
Date: Mon, 14 Dec 2020 21:14:02 +0000 [thread overview]
Message-ID: <X9fVmlPd1xbsVvET@breton.holly.idiocy.org> (raw)
In-Reply-To: <83h7ooaz1y.fsf@gnu.org>
On Mon, Dec 14, 2020 at 10:54:33PM +0200, Eli Zaretskii wrote:
> > Date: Mon, 14 Dec 2020 20:25:30 +0000
> > From: Alan Third <alan@idiocy.org>
> > Cc: konrad.podczeck@univie.ac.at, 42406@debbugs.gnu.org
> >
> > > However, this bug report said that scrolling becomes slower and slower
> > > with time, and that is not expected, and I see no direct relation
> > > between that and flickering. Can we please go back to that aspect of
> > > the problem? It shouldn't happen.
> >
> > I don't see any flickering. I only see the performance reduction when
> > multiple frames are open.
>
> If the performance hit is only a function of how many frames are
> there, then this is expected. I thought the performance got worse
> with time, but maybe I misunderstood.
I only see it as a function of how many frames are open. It doesn't
seem to get worse with time.
I guess we just add this but report to the list of complaints that the
NS port is terrible at drawing to the screen.
--
Alan Third
next prev parent reply other threads:[~2020-12-14 21:14 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 15:36 bug#42406: Mouse-wheel scrolling can be flickering Konrad Podczeck
2020-07-19 13:33 ` Alan Third
2020-07-19 20:29 ` Konrad Podczeck
2020-07-22 20:16 ` Alan Third
2020-07-30 10:30 ` Konrad Podczeck
2020-08-01 13:12 ` Alan Third
2020-10-10 9:51 ` Alan Third
2020-10-10 14:07 ` Konrad Podczeck
2020-12-10 17:14 ` Konrad Podczeck
2020-12-10 22:10 ` Alan Third
2020-12-11 8:18 ` Eli Zaretskii
2020-12-11 20:37 ` Alan Third
2020-12-13 19:05 ` Eli Zaretskii
2020-12-13 19:46 ` Alan Third
2020-12-14 0:20 ` Konrad Podczeck
2020-12-14 15:47 ` martin rudalics
2020-12-14 20:46 ` Konrad Podczeck
2020-12-15 7:58 ` martin rudalics
2020-12-15 13:27 ` Konrad Podczeck
2020-12-15 13:51 ` martin rudalics
2020-12-15 14:06 ` Konrad Podczeck
2020-12-15 15:20 ` martin rudalics
2020-12-15 19:31 ` Konrad Podczeck
2020-12-15 19:45 ` Eli Zaretskii
2020-12-15 19:52 ` Konrad Podczeck
2020-12-15 20:05 ` Eli Zaretskii
2020-12-15 20:12 ` Konrad Podczeck
2020-12-15 20:32 ` Eli Zaretskii
2020-12-16 8:46 ` martin rudalics
2020-12-16 15:58 ` Eli Zaretskii
2020-12-16 8:46 ` martin rudalics
2020-12-16 16:00 ` Eli Zaretskii
2020-12-16 16:53 ` martin rudalics
2020-12-16 17:18 ` Eli Zaretskii
2020-12-16 18:51 ` martin rudalics
2020-12-16 19:35 ` Eli Zaretskii
2020-12-17 7:29 ` martin rudalics
2020-12-16 20:29 ` Konrad Podczeck
2020-12-17 7:29 ` martin rudalics
2020-12-17 10:19 ` Konrad Podczeck
2020-12-17 13:21 ` martin rudalics
2020-12-17 14:44 ` Eli Zaretskii
2020-12-17 15:13 ` martin rudalics
2020-12-17 16:54 ` Eli Zaretskii
2020-12-17 17:34 ` martin rudalics
2020-12-17 18:01 ` Eli Zaretskii
2020-12-17 23:19 ` martin rudalics
2020-12-18 7:50 ` Eli Zaretskii
2020-12-18 8:39 ` martin rudalics
2020-12-18 11:45 ` Eli Zaretskii
2020-12-18 13:57 ` martin rudalics
2020-12-19 10:04 ` Eli Zaretskii
2020-12-17 16:40 ` Konrad Podczeck
2020-12-17 17:05 ` martin rudalics
2020-12-17 17:24 ` Eli Zaretskii
2020-12-17 14:04 ` Eli Zaretskii
2020-12-17 15:13 ` martin rudalics
2020-12-17 16:49 ` Eli Zaretskii
2020-12-17 17:34 ` martin rudalics
2020-12-16 21:31 ` Alan Third
2020-12-16 23:53 ` Konrad Podczeck
2020-12-15 16:52 ` Eli Zaretskii
2020-12-15 17:14 ` martin rudalics
2020-12-15 18:35 ` Eli Zaretskii
2020-12-14 16:17 ` Eli Zaretskii
2020-12-14 20:48 ` Konrad Podczeck
2020-12-14 21:01 ` Eli Zaretskii
2020-12-14 16:12 ` Eli Zaretskii
2020-12-14 20:25 ` Alan Third
2020-12-14 20:54 ` Eli Zaretskii
2020-12-14 21:14 ` Alan Third [this message]
2020-12-15 7:59 ` martin rudalics
2020-12-15 17:38 ` Alan Third
2020-12-15 18:54 ` martin rudalics
2020-12-15 19:50 ` Alan Third
2020-12-16 8:46 ` martin rudalics
2020-12-16 21:35 ` Alan Third
2020-12-17 17:47 ` Stefan Monnier
2020-12-17 18:16 ` Eli Zaretskii
2020-12-17 19:45 ` Stefan Monnier
2020-12-17 20:36 ` Eli Zaretskii
2020-12-17 21:07 ` Stefan Monnier
2020-12-18 7:43 ` Eli Zaretskii
2020-12-18 16:22 ` Stefan Monnier
2020-12-18 20:42 ` Eli Zaretskii
2020-12-18 23:12 ` Stefan Monnier
2020-12-19 7:44 ` Eli Zaretskii
2020-12-17 19:56 ` Stefan Monnier
2020-12-17 20:35 ` Stefan Monnier
2020-12-17 20:58 ` Eli Zaretskii
2020-12-17 21:24 ` Stefan Monnier
2020-12-18 7:46 ` Eli Zaretskii
2020-12-18 14:41 ` Stefan Monnier
2020-12-17 20:47 ` Eli Zaretskii
2020-12-17 23:19 ` martin rudalics
2020-12-17 23:24 ` Stefan Monnier
2020-12-17 23:29 ` Stefan Monnier
2020-12-18 7:56 ` martin rudalics
2021-05-21 10:23 ` bug#42406: macOS metal rendering engine in mac port Konrad Podczeck
2021-05-21 15:33 ` Aaron Jensen
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=X9fVmlPd1xbsVvET@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=42406@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=konrad.podczeck@univie.ac.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 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.