[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Missing display object API...
From: |
David Kastrup |
Subject: |
Re: Missing display object API... |
Date: |
Wed, 06 Sep 2006 17:14:32 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
address@hidden (Kim F. Storm) writes:
> David Kastrup <address@hidden> writes:
>
>> Correction: I meant (window-buffer (posn-window ...)), and it will not
>> work if the window configuration has changed since the click
>> registered. So probably instead of posn-object-overlay, one would
>> want posn-object-parent which returns either a buffer (when the origin
>> was from a text property) or an overlay (when the origin was from an
>> overlay).
>
> The redisplay engine doesn't store which "parent object" a given
> string or image belongs to, so making this possible is a major change.
>
> Let's reconsider it after the release.
Ok. A proper implementation might return a consed-up list of the
hierarchic history, so that we would get something like
(reverse '((#<window> (x . y)) (#<buffer> . pos) (#<overlay> . 'before-string)
(string . pos)))
as a result. This sort of posn-object-tree seems like a smarter idea
than just posn-object-parent (which might fall too short for some
applications). And it is certain to contain possibly required
information at some place.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum