On Tue, Jul 14, 2009 at 2:27 AM, Maximilian
Albert<maximilian.alb...@googlemail.com> wrote:
> Hi Patrick,
>
>>> Ah, okay. That's what I though. Out of interest: At the time when
>>> these elements get written into the SVG file, do they know about their
>>> mutual relationships? E.g., does a beam know which note heads it
>>> belongs to (or vice versa)?
>>
>> No.  The closest thing the elements possess that relates to this is
>> their *grob cause*.  For example the NoteHead grob is often the grob
>> cause for the "noteheads.s2" glyph.
>
> OK, thanks for the explanation. I seem to remember that some time ago
> I was in a similar situation, where I wanted to find out some
> elements' parent(s) from my code but was unable to, probably for
> precisely this reason. Do you happen to know at what stage of the
> engraving process elements are aware of their mutual relationships,
> just in case I stumble across this problem again in the future?

I don't know for sure, but I would guess that these relationships are
set in the engraving/acknowledging step, and that they lose the
relationships after they have been converted to stencils (the post
page-breaking step, I think).

HTH,
Patrick


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to