Kieren MacMillan <kieren_macmil...@sympatico.ca> writes: > Hi all, > >>> I think that issue 3518 (pushed recently) does just this: >>> https://code.google.com/p/lilypond/issues/detail?id=3518 >> >> It doesn't do the automatic "AI nightmare" part. > > Yes, unfortunately... > >> However, it provides the low level machinery for pulling in the >> "maximally required" number >> of staves between automatic or manual line breaks, where the requirement >> is determined by working with keep-alive-interfaces and tags on the >> various staff variants. > > That could be helpful! > > I still need to wrap my head around how this framework/machinery works > (or doesn’t) with true content-presentation separation; the example on > the Google Code page has multiple "\context Staff” calls buried in the > \violins note definition, which to my mind mixes content with > presentation in an unfortunate way.
The example attached to the last comment of the related issue <URL:https://code.google.com/p/lilypond/issues/detail?id=2779> goes a bit further towards creating an ad-hoc interface rather than just pulling the low-level levers. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
