Am Sonntag, 26. Juni 2011, 13:34:20 schrieben Sie: > I'm afraid this fails `make check'. > dynamics-alignment-no-line-linebreak.ly weirdly works directly without a > hitch, but crashes under test conditions: > > Processing `./1e/lily-b9dc92b9.ly' > Parsing... > Renaming input to: `dynamics-alignment-no-line-linebreak.ly' > Interpreting music... > Preprocessing graphical objects... > Calculating line breaks... > Drawing systems... > Writing header field `texidoc' to `./1e/lily-b9dc92b9.texidoc'... > Writing ./1e/lily-b9dc92b9-1.signature > Writing ./1e/lily-b9dc92b9-2.signatureUnbound variable: open-file > Unbound variable: open-file > ERROR: In procedure ly_grob_extent: > ERROR: Wrong type argument in position 2 (expecting common refpoint): > #<Grob System >
Hmm, again the problem is that the parts after a line break of broken dynamic spanners (text / hairpin) do not have any parent set any more... Now, the function write-system-signature (subfunction found-grob, stencil.scm) calls ly:grob-extent, which checks for the common refpoint of the spanner and its parent (which is 0)... So, I more and more get the impression that the approach of simply killing the line spanner and letting its child dynamic spanners live on is the wrong approach to \breakDynamicSpan and spanner's style=#'none... Cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
