From: Eli Zaretskii <eliz@gnu.org>
To: joakim@verona.se
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: how to find out when display property is deleted in C?
Date: Tue, 13 May 2008 21:53:03 +0300 [thread overview]
Message-ID: <u8wyekpdc.fsf@gnu.org> (raw)
In-Reply-To: <m3fxsmhevf.fsf@verona.se>
> From: joakim@verona.se
> Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
> cc: emacs-devel@gnu.org
> Date: Tue, 13 May 2008 08:55:48 +0200
>
> > Forgive me for chiming into a discussion I wasn't following about a
> > subject that I'm mostly ignorant about, but: when the display property
> > goes away, Emacs triggers a redisplay the next moment it doesn't have
> > anything more important to do. That redisplay should supply you with
> > an event to remove the gtk widgets, no? Just plug your
> > widget-removing routines into the code that runs during redisplay.
>
> I tried this and I'm still having difficulties. The redisplay
> code optimizes drawing. It appears these optimizations make it so the
> xwidget glyph draw routine isnt allways called on redisplay.
Search xdisp.c for "optimiz", and you will find quite a few ways of
turning off these optimizations. For example, you could set the
prevent_redisplay_optimizations_p flag of the buffer, or set the value
of this_line_start_pos variable non-positive. It could be that this
works, but makes redisplay painfully slow, in which case less naive
coding will be needed to turn off optimizations only sometimes. But
at least you will know that it works; I was taught to make it right
before I make it fast.
prev parent reply other threads:[~2008-05-13 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 9:34 how to find out when display property is deleted in C? joakim
2008-05-12 14:25 ` Stefan Monnier
2008-05-12 14:58 ` joakim
2008-05-12 16:57 ` Stefan Monnier
2008-05-12 20:08 ` Eli Zaretskii
2008-05-13 6:55 ` joakim
2008-05-13 18:53 ` Eli Zaretskii [this message]
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=u8wyekpdc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=monnier@iro.umontreal.ca \
/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.