Kieren MacMillan <[email protected]> writes: > Hello all, > > We can temporarily change the direction of many grobs — Scripts, TextScripts, > etc. — such that the usual effect is that they flip from being (e.g.,) > beneath a context (e.g., the Staff that the Voice is a child of) to being > above that context. > > I’m wondering — brainstorming mode now — if there’s an easy way to extend > that concept to contexts which ARE NOT contained by another context (as in > the Voice ∈ Staff example, above), but rather are adjacent to a second > context. One obvious example is: > > << > \new Staff \someNotes > \new Lyrics \someWords > >> > > If there were a small number of words that needed to be above the Staff, the > current workaround is to add a whole new context, e.g., > > << > \new Lyrics \someWordsAbove > \new Staff \someNotes > \new Lyrics \someWordsBelow > >> > > adjust staff-affinity/ies and add spacer rests as/if necessary, > etc. Why [technically] can we not say, “\once \override > LyricText.alignAboveContext = …” to move the attachment of that grob > to “the other side” of the Staff context it is normally associated > with and adjacent to.
Because there is only one VerticalAxisGroup associated with the context. You can try creating a SubLyrics context and then to a \change Lyrics = ... command for moving it into another Lyrics context. -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
