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: jdtsmith@gmail.com, emacs-devel@gnu.org
Subject: Re: Drawing UI elements behind text
Date: Wed, 27 Nov 2024 20:58:33 +0200	[thread overview]
Message-ID: <86bjy0fqqu.fsf@gnu.org> (raw)
In-Reply-To: <b27f4d2f-95d4-405d-8119-d1abb022d1b4@imayhem.com> (message from Cecilio Pardo on Wed, 27 Nov 2024 19:28:58 +0100)

> Date: Wed, 27 Nov 2024 19:28:58 +0100
> Cc: jdtsmith@gmail.com, emacs-devel@gnu.org
> From: Cecilio Pardo <cpardo@imayhem.com>
> 
> > If they are completely disconnected, how does this work when the
> > window is scrolled several lines?
> 
> They are anchored at locations on the buffer, specified by line/column. 
> This is transformed into pixels using the size of the default char cell 
> for the buffer.  The buffer scroll position on each window is used to 
> compute the final position on the frame/screen.
> 
> For buffers that use different font sizes or images this is probably not 
> very useful. Direct pixel positions can be used too.
> 
> 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?



  reply	other threads:[~2024-11-27 18:58 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 [this message]
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
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=86bjy0fqqu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cpardo@imayhem.com \
    --cc=emacs-devel@gnu.org \
    --cc=jdtsmith@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).