unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arthur Miller <arthur.miller@live.com>
Cc: tomas@tuxteam.de, emacs-devel@gnu.org
Subject: Re: Emacs canvas support
Date: Thu, 30 Apr 2020 17:18:55 +0300	[thread overview]
Message-ID: <83v9lhvyy8.fsf@gnu.org> (raw)
In-Reply-To: <AM0PR06MB6420DD820E92495E105B808E96AA0@AM0PR06MB6420.eurprd06.prod.outlook.com> (message from Arthur Miller on Thu, 30 Apr 2020 15:11:10 +0200)

> From: Arthur Miller <arthur.miller@live.com>
> Date: Thu, 30 Apr 2020 15:11:10 +0200
> Cc: tomas@tuxteam.de, emacs-devel@gnu.org
> 
> I have a question here about display: when lisp engine decides to draw
> the display, how difficult would it be to add a callback for pre- and
> post render?

I don't think I understand the question.  It is trivial to add a call
to a Lisp function anywhere in Emacs, the question is what that
function will be able to do to be useful.  If the called Lisp can do
anything it wants, then how can it be useful without knowing a whole
lot about the window layout, and what was just now, or will be in a
moment, drawn on it, and in which parts?

> Prerender callback could be any user lisp function called
> that do anything it wants, say draw something on the screen as it owned
> window itself. Than render engine would it's ordinary rendering drawing
> just as it does now, pretending that there was nothing already drawn, so
> it would mean no change at all to current c code for rendering.

So how do we prevent the display engine from blissfully drawing over
what the pre-render draws?

> Similarly one call a post-render callback and draw over the already
> rendered text so user could draw whatever on top of already draw
> onverlas and what not.

How will the post-render know where it can and where it cannot draw?
Or even where to draw, for that matter (assuming you want to do
something more useful than just put the same pixels in the same pixel
coordinates)?  For example, if the window scrolls, wouldn't you want
the graphics drawn by these pre/post-renderers to move on display as
well, at least sometimes?  If you do, how can you do that without
knowing some details about the scroll?

> It is just how z-buffer works and it would mean z order from pre-render,
> normal render (as it is now) and post render as implicit z-depths.

AFIU, z-buffer doesn't care to obscure what's displayed below.  is
this what you have in mind: obscuring the "normal" display with some
graphics?



  reply	other threads:[~2020-04-30 14:18 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <875zdikdge.fsf.ref@yahoo.com>
2020-04-29  6:34 ` Emacs canvas support Po Lu via Emacs development discussions.
2020-04-29  8:24   ` Eli Zaretskii
2020-04-29  9:57     ` Po Lu
2020-04-29 10:10       ` Eli Zaretskii
2020-04-29 10:22         ` Po Lu
2020-04-29 10:27           ` Po Lu via Emacs development discussions.
2020-04-29 11:47             ` Eli Zaretskii
2020-04-29 10:35           ` Eli Zaretskii
2020-04-29 10:41             ` Po Lu
2020-04-29 11:51               ` Eli Zaretskii
2020-04-29 12:12                 ` Po Lu
2020-04-29 16:14               ` David Engster
2020-04-29 16:54                 ` Eli Zaretskii
2020-04-29 17:16                   ` tomas
2020-04-29 17:27                     ` Eli Zaretskii
2020-04-29 17:38                       ` Eli Zaretskii
2020-04-30 13:11                         ` Arthur Miller
2020-04-30 14:18                           ` Eli Zaretskii [this message]
2020-04-30 14:58                             ` Arthur Miller
2020-04-30 17:30                               ` Eli Zaretskii
2020-05-01 14:32                                 ` Arthur Miller
2020-04-29 18:51                       ` tomas
2020-04-29 19:03                         ` Eli Zaretskii
2020-04-29 19:08                           ` tomas
2020-04-29 19:25                             ` Eli Zaretskii
2020-04-29 19:59                               ` tomas
2020-04-30  1:19                                 ` Stefan Monnier
2020-04-30  6:55                                   ` tomas
2020-04-30 12:03                                     ` Stefan Monnier
2020-04-30 12:50                                       ` tomas
2020-04-30  8:04                                   ` Po Lu
2020-04-30 12:08                                     ` Stefan Monnier
2020-04-30 13:55                                     ` Eli Zaretskii
2020-05-01 23:27                                       ` Po Lu
2020-05-02  6:51                                         ` Eli Zaretskii
2020-04-30 13:46                                   ` Eli Zaretskii
2020-04-30 14:37                                     ` Stefan Monnier
2020-04-30 17:27                                       ` Eli Zaretskii
2020-04-30 18:22                                         ` Stefan Monnier
2020-04-30 18:42                                           ` Eli Zaretskii
2020-04-30 14:27                                   ` Drew Adams
2020-04-30 13:33                                 ` Eli Zaretskii
2020-04-30 13:52                                   ` Arthur Miller
2020-04-29 19:23                   ` David Engster
2020-04-30 13:29                     ` Eli Zaretskii
2020-04-30  6:52                   ` Corwin Brust
2020-04-29 17:08                 ` Eli Zaretskii
2020-04-29 20:14                   ` David Engster
2020-04-30 13:35                     ` Eli Zaretskii
2020-04-29 20:48   ` Juri Linkov
2020-04-30  2:36     ` Eli Zaretskii
2020-04-30 20:20       ` Juri Linkov
2020-05-01  6:01         ` Eli Zaretskii

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=83v9lhvyy8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=arthur.miller@live.com \
    --cc=emacs-devel@gnu.org \
    --cc=tomas@tuxteam.de \
    /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).