unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Stipples and scroll optimizations
Date: Sun, 08 May 2022 17:20:14 +0800	[thread overview]
Message-ID: <87sfpk4bzl.fsf@yahoo.com> (raw)
In-Reply-To: <83ee14wfzc.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 08 May 2022 12:06:31 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Sorry, I don't understand: what is the "previous" glyph matrix, and
> how can you use it for this test?

I mean the glyph matrix representing what is currently on the glass, the
"current matrix".

> Really?  I see that 'struct face' has a 'stipple' member, which is set
> in realize_gui_face, and that happens when we realize the face, long
> before x_draw_glyph_string is called.  And each glyph in a glyph_row
> has a face_id member, which allows you to get at the corresponding
> face structure.  Why cannot you use this to detect glyph_row's that
> use stipples?  The only type of glyph whose stipple is ignored is the
> cursor glyph, and that hardly matters for your purposes here, no?

Whether or not a stipple is present usually depends on the `stippled_p'
flag, which is set in `x_set_glyph_string_gc'.  But for starters,
drawing an image glyph might change that flag, and an image might also
obscure the stipple entirely, in which case we don't want to inhibit the
scrolling optimization.



  reply	other threads:[~2022-05-08  9:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87a6bs5w05.fsf.ref@yahoo.com>
2022-05-08  7:22 ` Stipples and scroll optimizations Po Lu
2022-05-08  7:30   ` Eli Zaretskii
2022-05-08  7:34     ` Po Lu
2022-05-08  7:40       ` Eli Zaretskii
2022-05-08  7:58         ` Po Lu
2022-05-08  9:06           ` Eli Zaretskii
2022-05-08  9:20             ` Po Lu [this message]
2022-05-08 10:46               ` Eli Zaretskii
2022-05-08 10:59                 ` Po Lu
2022-05-08 11:29                   ` Eli Zaretskii
2022-05-08 11:46                     ` Po Lu
2022-05-08 11:07                 ` Po Lu

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=87sfpk4bzl.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --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).