unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Analysis of redisplay performance on Windows
Date: Mon, 28 Jul 2008 08:04:46 +0100	[thread overview]
Message-ID: <488D6F8E.8080502@gnu.org> (raw)
In-Reply-To: <8763qqiz6j.fsf@stupidchicken.com>

Chong Yidong wrote:
> Jason Rumney <jasonr@gnu.org> writes:
> 
>> As I suggested in my earlier email, new functions in the
>> font backend interface to select a font for working with and releasing
>> it when done, would help, as we could then skip doing this in
>> functions like encode_char and text_extents.
> 
> Could you suggest precisely what interface we need?  I.e., could you
> suggest function names and rough docstrings?

/* Optional.
   Begin using a font exclusively.
   Backends may setup the FONT for use on frame F here so that it
   does not need setting up in every call to the encode_char,
   text_metrics or draw functions.  The font remains current
   until done_font is called.  */
   functions.
void (*use_font) P_ ((FRAME_PTR f, struct font *font));

/* Optional.
   Finish using a font exclusively.
   Backends may undo the actions of use_font here.  */
void (*done_font) P_ ((FRAME_PTR f, struct font *font));





  parent reply	other threads:[~2008-07-28  7:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27  3:07 Analysis of redisplay performance on Windows Chong Yidong
2008-07-27  9:55 ` Jason Rumney
2008-07-27 20:56   ` Chong Yidong
2008-07-27 21:30     ` Jason Rumney
2008-07-27 21:40       ` Chong Yidong
2008-07-27 21:53         ` Jason Rumney
2008-07-28  1:18           ` Chong Yidong
2008-07-28  3:06             ` Adrian Robert
2008-07-28  5:03               ` Chong Yidong
2008-07-28  7:04             ` Jason Rumney [this message]
2008-07-28  2:11           ` Kevin Yu
2008-07-28  4:24           ` YAMAMOTO Mitsuharu
2008-07-28  9:48             ` YAMAMOTO Mitsuharu
2008-07-30 21:51               ` Jason Rumney

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=488D6F8E.8080502@gnu.org \
    --to=jasonr@gnu.org \
    --cc=cyd@stupidchicken.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).