unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: emacs-devel@gnu.org
Subject: Re: Drawing UI elements behind text
Date: Wed, 27 Nov 2024 22:12:49 +0200	[thread overview]
Message-ID: <861pywfnb2.fsf@gnu.org> (raw)
In-Reply-To: <943ad61e-9823-4dff-b8c0-d9d1b74ef676@imayhem.com> (message from Cecilio Pardo on Wed, 27 Nov 2024 21:01:42 +0100)

> Date: Wed, 27 Nov 2024 21:01:42 +0100
> From: Cecilio Pardo <cpardo@imayhem.com>
> 
> On 27/11/2024 19:58, Eli Zaretskii wrote:
> 
> >> They are drawn after switching the back paint buffer, so that the
> >> redisplay result is left alone.
> > 
> > So you clear them up when redisplay starts and then redraw them in
> > their entirety when it ends, something like that?  Doesn't that slow
> > down redisplay, especially if there are many pixels and a large
> > window?
> 
> Yes. We do a full frame copy on each double buffered redisplay, I expect 
> we can add this with reasonable impact.
> 
> The very naive implementation I have now adds something like 5ms to each 
> redisplay on a 1900px frame, and I hope to bring it down a lot from there.

What takes 5ms, exactly? what kind of redisplay did you trigger, and
how did you trigger it?



  reply	other threads:[~2024-11-27 20:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 16:39 Drawing UI elements behind text Cecilio Pardo
2024-11-10 18:09 ` Jim Porter
2024-11-10 18:44   ` Eli Zaretskii
2024-11-10 19:06     ` Jim Porter
2024-11-10 19:22       ` Eli Zaretskii
2024-11-10 19:29         ` Jim Porter
2024-11-10 19:42           ` Eli Zaretskii
2024-11-24 23:37 ` JD Smith
2024-11-26 23:19   ` Cecilio Pardo
2024-11-27 14:36     ` Eli Zaretskii
2024-11-27 18:28       ` Cecilio Pardo
2024-11-27 18:58         ` Eli Zaretskii
2024-11-27 20:01           ` Cecilio Pardo
2024-11-27 20:12             ` Eli Zaretskii [this message]
2024-11-27 20:30               ` Cecilio Pardo
2024-11-28  6:53                 ` Eli Zaretskii
2024-11-28  8:43                   ` Cecilio Pardo
2024-11-28  9:57                     ` Eli Zaretskii
2024-11-28 10:41                       ` Cecilio Pardo
2024-11-28 11:56                         ` Eli Zaretskii
2024-11-28 12:09                           ` Cecilio Pardo
2024-11-27 21:15           ` JD Smith
2024-11-27 21:47             ` Cecilio Pardo
  -- strict thread matches above, loose matches on Subject: below --
2024-11-27  2:31 JD Smith
2024-11-27 18:33 ` Cecilio Pardo

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=861pywfnb2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cpardo@imayhem.com \
    --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).