From: Kenichi Handa <handa@m17n.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: adrian.b.robert@gmail.com, emacs-devel@gnu.org
Subject: Re: font-backend mechanism on Windows and Mac?
Date: Sat, 15 Sep 2007 11:24:15 +0900 [thread overview]
Message-ID: <E1IWNKR-0004wN-H7@etlken.m17n.org> (raw)
In-Reply-To: <46EA9371.7020701@gnu.org> (message from Jason Rumney on Fri, 14 Sep 2007 14:58:09 +0100)
In article <46EA9371.7020701@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:
> Kenichi Handa wrote:
> > Do you mean that the displaying got slower after the recent
> > change?
> Perhaps, it does seem a little slower, and the more complex clipping
> masks might have caused that, but I think most of the slowness is from
> the new font-backend itself. It seems to be outputting a character at a
> time, rather than whole lines. It might be due to a workaround in the
> Windows code to avoid a Cleartype bug in the old font code (though I'd
> expect the old code to be similarly slow in that case), or it might be
> not combining multiple redraw requests as the overlapping window is
> moved over the Emacs frame.
As I wrote before, metrics calculation is done one glyph by
one, but rendering is done for a block of glyphs (i.e. those
in one "struct glyph_string").
Anyway, while debugging the previous problem, I found that
the display engine (regardless of font-backend) does lots of
unnecessary clipping for exposing. But, improving it
requires rather big changes.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2007-09-15 2:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 2:39 font-backend mechanism on Windows and Mac? Kenichi Handa
2007-09-10 3:04 ` YAMAMOTO Mitsuharu
2007-09-10 3:12 ` Kenichi Handa
2007-09-10 3:47 ` YAMAMOTO Mitsuharu
2007-09-10 4:37 ` Kenichi Handa
2007-09-10 12:39 ` Adrian Robert
2007-09-10 13:09 ` Kenichi Handa
2007-09-11 21:04 ` Adrian Robert
2007-09-11 21:21 ` Stefan Monnier
2007-09-12 13:51 ` Adrian Robert
2007-09-10 7:42 ` Jason Rumney
2007-09-10 13:13 ` Kenichi Handa
2007-09-10 13:45 ` Jason Rumney
2007-09-10 13:49 ` Jason Rumney
2007-09-12 6:43 ` Kenichi Handa
2007-09-13 11:55 ` Kenichi Handa
2007-09-13 13:41 ` Jason Rumney
2007-09-14 12:46 ` Kenichi Handa
2007-09-14 13:58 ` Jason Rumney
2007-09-14 23:10 ` Adrian Robert
2007-09-14 23:56 ` Jason Rumney
2007-09-15 1:31 ` Kenichi Handa
2007-09-15 7:37 ` Jason Rumney
2007-09-16 10:29 ` Kenichi Handa
2007-09-16 11:01 ` Jason Rumney
2007-09-17 2:16 ` Kenichi Handa
2007-09-15 2:24 ` Kenichi Handa [this message]
2007-09-13 15:53 ` Adrian Robert
2007-09-13 16:23 ` Jason Rumney
2007-09-14 1:19 ` Kenichi Handa
2007-09-14 13:52 ` Adrian Robert
2007-09-14 14:55 ` YAMAMOTO Mitsuharu
2007-09-14 15:02 ` Jason Rumney
2007-09-14 15:36 ` YAMAMOTO Mitsuharu
2007-09-15 0:05 ` Adrian Robert
2007-09-15 1:44 ` YAMAMOTO Mitsuharu
2007-09-15 13:21 ` Adrian Robert
2007-09-15 13:43 ` YAMAMOTO Mitsuharu
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=E1IWNKR-0004wN-H7@etlken.m17n.org \
--to=handa@m17n.org \
--cc=adrian.b.robert@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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).