Simon Albrecht <simon.albre...@mail.de> writes: > Am 26.08.2015 um 18:52 schrieb David Kastrup: >> New issue 4577 >> >> Status: Started >> Summary: Add StaffAxis context type >> Tags: Type-Enhancement Patch-new >> >> Rietveld issue: 265730043 (https://codereview.appspot.com/265730043) >> Issue description: >> Add StaffAxis context type See the regression test for more info. > Another naming suggestion: MixedLine (or SystemLine? > LineContainer?). IMO ‘line’ gives a better impression of the > ‘container’ character than ‘axis’. And after all, it might be used for > contexts without a Staff.
So may be a StaffGroup, a GrandStaff, a ChoirStaff. And all of those are containers of Staff contexts. I'm not married to the Axis bit, but the common trait _is_ every stafflike entity inside sharing a common axis, whether simultaneously or sequentially. > Eventually, this should be documented within a new subsection to NR > 1.6.1 > <http://lilypond.org/doc/v2.19/Documentation/notation/displaying-staves>. Definitely. I wanted to change the existing example (part of which made it into the regtest) but found that it was gone, with the exception of some outdated translations. > Good idea! Well, it arose in some user list discussion: instead of adding somewhat strange \accepts to Staff, it may be better to have one enclosing context. That's more of a stock tool rather than having to tweak contexts yourself. In addition, in that way the Staff context does not get to see events it is not suited for. Having a ChordNames context inside of a Staff context, for example, works almost more by chance than by design since the Staff context gets to see all the same events. But since at least the NoteHeadEngraver (?) sits at Voice level, one does not get to see much from this problem. But an independent context is nicer. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
