Making a \layout definition in Scheme (was: edition-engraver and multiple scores)

2018-04-04 Thread Urs Liska
Am 04.04.2018 um 12:17 schrieb Urs Liska: Am 04.04.2018 um 10:32 schrieb Jan-Peter Voigt: ... there is a function ly:score-add-output-def! to add layout- and midi-blocks to a score object. Cheers Jan-Peter Thanks, this finally is what I should have been looking for! Bess Urs OK, but

Re: edition-engraver and multiple scores

2018-04-04 Thread Urs Liska
Am 04.04.2018 um 10:32 schrieb Jan-Peter Voigt: ... there is a function ly:score-add-output-def! to add layout- and midi-blocks to a score object. Cheers Jan-Peter Thanks, this finally is what I should have been looking for! Bess Urs ___

Re: edition-engraver and multiple scores

2018-04-04 Thread Jan-Peter Voigt
... there is a function ly:score-add-output-def! to add layout- and midi-blocks to a score object. Cheers Jan-Peter Am 3. April 2018 11:34:58 MESZ schrieb Urs Liska : >I ran into an issue with the edition-engraver, targeting individual >scores when multiple scores are

Re: edition-engraver and multiple scores

2018-04-03 Thread Jan-Peter Voigt
... and to add the editionID with ly:make-score there are parameters to achieve that. The editionID is also a context prop. You might look up the code of editionID. And maybe the lalily templates give some inspiration. (I moved it oll recently) Am 3. April 2018 11:34:58 MESZ schrieb Urs Liska

Re: edition-engraver and multiple scores

2018-04-03 Thread Jan-Peter Voigt
Hi Urs, I am not at my desk right now, but IISC you named the right thing: Every score needs its own ID so that the EE is able to target the right score. We might *additionally* store mods as a Score context prop. for certain use cases. But still I strongly vote for IDs per score. Jan-Peter

edition-engraver and multiple scores

2018-04-03 Thread Urs Liska
I ran into an issue with the edition-engraver, targeting individual scores when multiple scores are compiled within a bookpart. It's actually within the 'page-layout' or rather the 'breaks' openLilyLib package, and I can imagine that my issue is related to another one that was raised recently