From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Adrian Robert <adrian.b.robert@gmail.com>
Cc: 2530@emacsbugs.donarmstrong.com,
David Reitter <david.reitter@gmail.com>,
Chong Yidong <cyd@stupidchicken.com>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: 23/NS: redraws according to mouse-face are slow
Date: Wed, 06 May 2009 11:25:35 +0900 [thread overview]
Message-ID: <wly6tbt1b4.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <B2B56BBA-6285-48DE-8C95-3BBCA4805146@gmail.com>
>>>>> On Wed, 6 May 2009 08:55:36 +0700, Adrian Robert <adrian.b.robert@gmail.com> said:
>> The effect of ns_update_begin seems to avoid -[NSWindow
>> flushWindow] call (via ns_unfocus) for each ns_draw_glyph_string
>> call. Does this frequent flushing necessary in the first place?
>> Other terms don't seem to do flushing for each string drawing call.
> My assumption was that it is legal to call draw_glyph_string()
> outside of an update_begin()-end() pair. So draw_glyph_string()
> must be able to operate in "self-contained" mode, which and the
> flush is needed. The same logic holds for other RIF functions --
> that they can either be called in one-shot mode or in batch mode
> (inside update begin-end). In the latter case, focus/unfocus
> reflect the batching by holding screen flush until end.
Other terms don't do flushing even at update_end, let alone at the end
of each one-shot drawing operation (you may see XFlush calls in the
code but they are mostly defined as no-ops). IIUC, flushing happens
only by explicit flush_display(_optional) RIF calls or at the timing
of polling/receiving window system events (e.g., XPending on X11, and
ReceiveNextEvent on Carbon) implicitly.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2009-05-06 2:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 21:29 bug#2530: 23/NS: redraws according to mouse-face are slow Adrian Robert
2009-04-20 18:01 ` David Reitter
2009-04-20 18:01 ` David Reitter
2009-04-24 3:27 ` Adrian Robert
2009-05-04 22:55 ` bug#2530: " David Reitter
2009-05-04 22:55 ` David Reitter
2009-05-04 23:24 ` Leo
2009-05-05 1:53 ` Chong Yidong
2009-05-05 3:37 ` bug#2530: " David Reitter
2009-05-05 3:37 ` David Reitter
2009-05-05 10:36 ` Adrian Robert
2009-05-05 14:13 ` Chong Yidong
2009-05-05 17:32 ` David Reitter
2016-01-14 5:08 ` bug#2530: " Andrew Hyatt
2016-01-14 5:08 ` Andrew Hyatt
2016-01-14 20:34 ` Alan J Third
2016-01-14 21:00 ` David Reitter
2016-01-14 21:00 ` David Reitter
2016-01-14 21:39 ` Christian Kruse
2016-01-15 7:38 ` Eli Zaretskii
2016-01-15 7:38 ` Eli Zaretskii
2016-01-16 4:15 ` Andrew Hyatt
2016-01-16 4:15 ` Andrew Hyatt
2016-01-14 21:39 ` Christian Kruse
2009-05-05 17:32 ` David Reitter
2009-05-06 1:47 ` Stefan Monnier
2009-05-06 1:47 ` Stefan Monnier
2009-05-06 7:40 ` YAMAMOTO Mitsuharu
2009-05-06 7:40 ` bug#2530: " YAMAMOTO Mitsuharu
2009-05-05 14:13 ` Chong Yidong
2009-05-06 0:50 ` YAMAMOTO Mitsuharu
2009-05-06 0:50 ` YAMAMOTO Mitsuharu
2009-05-06 1:55 ` Adrian Robert
2009-05-06 2:25 ` YAMAMOTO Mitsuharu [this message]
2009-05-06 2:25 ` bug#2530: " YAMAMOTO Mitsuharu
2009-05-06 1:55 ` Adrian Robert
2009-05-05 10:36 ` Adrian Robert
2009-05-05 1:53 ` Chong Yidong
2009-04-24 3:27 ` Adrian Robert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wly6tbt1b4.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=2530@emacsbugs.donarmstrong.com \
--cc=adrian.b.robert@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=david.reitter@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.