Le 17 août 09 à 09:23, Nicolas Sceaux a écrit :
Le 17 août 09 à 02:41, Reinhold Kainhofer a écrit :Hmm, to me it seems that you are effectively calling the parser to interpret \include "file.ly". That is a nice way around my problem, where only the parser seems to have a pointer to the current book (so you are invoking the parser to insert the scores into the bookpart), but it can't be used in my case.My problem is that I don't have the score in a file in lilypond syntax at all. I have only the notes of the individual instruments, but the whole score (containing part-combined staves, etc.) is really generated on-the- fly inscheme.If you look at the definition of `bookpart-score-handler' in my file, you see that the book-part argument is not used. Instead, all scores are added to the toplevel-scores parser variable (even though they are not really toplevel, it does not matter). The `toplevel-bookpart-handler' then uses this variable to actually add the scores to the bookpart. This function is called by the parser when a \bookpart block is closed, so at this point the bookpart object is known. You can change the book-score-handler and toplevel-book-handler to act the same way.
Here is a short example showing how that may be done.
scheme-book-scores.ly
Description: Binary data
<<inline: scheme-book-scores.png>>
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
