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: Thu, 28 Nov 2024 13:56:54 +0200 [thread overview]
Message-ID: <86y113d115.fsf@gnu.org> (raw)
In-Reply-To: <f2dcbf18-d9a3-451c-b0d4-b6dcfa8fdc41@imayhem.com> (message from Cecilio Pardo on Thu, 28 Nov 2024 11:41:25 +0100)
> Date: Thu, 28 Nov 2024 11:41:25 +0100
> Cc: emacs-devel@gnu.org
> From: Cecilio Pardo <cpardo@imayhem.com>
>
> On 28/11/2024 10:57, Eli Zaretskii wrote:
> >> The segments are drawn independently of redisplay, on top of its result,
> >> without affecting it (so that the next redisplay finds it exactly as it
> >> was). So no optimizations are disabled, and the time added by them is
> >> independent of what redisplay had to do.
> >
> > I'm probably missing something: if Emacs uses the scroll_run_hook,
> > which bitblts a portion of the screen's pixels, doesn't that move also
> > the pixels of the segments? If not, does it mean those segments'
> > pixels are not drawn on the screen, but somehow overlaid on it using
> > some video driver trick?
>
> This is working only if emacs is using a double buffered configuration.
> Redisplay works on the back buffer, where we don't draw anything. When
> the back buffer goes to the screen, we add the segments to the screen.
> scroll_run_hook works on the back buffer.
I see. So the display code basically knows nothing about these
segments? And you need to redraw them in their entirety each
redisplay cycle?
next prev parent reply other threads:[~2024-11-28 11:56 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
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 [this message]
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=86y113d115.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).