Hi all,
>/However, I would like to avoid the Dynamics layer, because it introduces /
>/redundancy./
>/Is there a way to achieve the same result without that layer?/
If you want to really make Lilypond leap forward as an engraving tool, figure
out a way to allow a grob (in this case a pedal bracket) to be "pushed" from
one context (in this case a Staff) to another [adjacent? arbitrary?!] context
(in this case a Dynamics). Then we’d all have the best of both worlds: complete
context-ual flexibility with no redundancy. =)
We already have "\change Staff"… Surely this can’t be that hard?!
(Note: If I could *find* the definition of "change" in the code, I might be
able to do it myself. Apparently my search-fu is weak.)
Cheers,
Kieren.
Hi,
While I have no clue about where \change is actually defined (as
it isn't a music function), you may want to have a look at
lily/change-iterator.cc,lily-change-sequence-iterator.cc as well as
scm/ly-syntax-constructors.scm line 155.
That said, changing a grob's context is very different from
changing a context's parent. I don't know where typesetting
decisions would then be made nor the precise consequences
it would actually entail.
Best,
Jean Abou Samra
