Valentin Villenave <valen...@villenave.net> writes:
> On Thu, Oct 31, 2013 at 12:24 PM, David Kastrup <d...@gnu.org> wrote:
>> First you have to figure out what you want to happen here. Do you want
>> two Dynamics contexts with different orientation and settings? In that
>> case, you'll need to provide a superior context aliased to Staff where
>> it can anchor those Dynamics contexts.
>
> I still must be missing something: in the following example, the new
> dynamics-"voice" context is created *below* the PianoStaff, and not
> inserted inside the DynamicsStaff context as intended.
>
> \layout {
> \context {
> \type "Engraver_group"
> \name "DynamicsStaff"
> \alias "Staff"
> \accepts "Dynamics"
> \defaultchild "Dynamics"
> }
> \context {
> \PianoStaff
> \accepts DynamicsStaff
> %\denies Dynamics % doesn't change anything here.
> }
> }
Well, if you now remove the Axis_group_engraver from Dynamics and add it
to \DynamicsStaff, your results will be more consistent as no new axis
groups get started. However, conflicting dynamics specifications will
get pasted over each other.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
