On Tue, Apr 11, 2017 at 5:54 PM, Urs Liska <u...@openlilylib.org> wrote: > > > Am 11.04.2017 um 21:04 schrieb tisimst: > > > > On Tue, Apr 11, 2017 at 1:00 PM, Urs Liska [via Lilypond] <[hidden email]> > wrote: >> >> >> >> Am 11.04.2017 um 20:46 schrieb Malte Meyn: >> > >> > Am 11.04.2017 um 20:36 schrieb Urs Liska: >> >> So, is there any moment in the compilation process where the natural, >> >> unstretched length of a measure can be calculated? It doesn't have to >> >> be >> >> an easily-read property and can involve calculation, but actually the x >> >> position of the barlines would be an easy target - *if* there's this >> >> magic moment in the compilation pipeline ;-) >> > Maybe you could experiment with the ly:one-line-breaking? >> >> I don't think so (only, of course, to investigate how much can be done >> on the internal level). >> Basically what I'm after is a ly:cheap-line-breaking mode that doesn't >> care at all about overall appearance or good page turns but instead >> simply places as many measures in a line as fit naturally. If then a >> line break changes and I know the natural width of the measures I can >> determine before compilation how many measures will fit on the *next* >> system.
But given clefs, key signatures, cautionaries, doesn't this mean that you need to know the width of any measure as the first measure of the line, as the last measure on a line, at a median position? I'm not clear on the need to know how many measures will fit on subsequent lines before compilation. Is it so that you can compile by system? (Just trying to get a handle on your goals so I can help better.) David _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
