>> I've added a general event class, BreakSpanEvent, as the parent
>> class of BreakDynamicSpanEvent since I'd eventually like to
>> implement commands analogous to \breakDynamicSpan for some of the
>> other alignment spanners (e.g., pedals and figured bass).
>
> Awesome, thanks for your work, Neil! Just one question: Why is it
> necessary to explicitly specify the \breakDynamicSpan command? As a
> user, I would normally not include it since I'm not aware of it and
> would thus think that manual positioning of hairpins simply doesn't
> work (or is buggy). Is there a way to avoid it (e.g., by having
> Lilypond automatically detect when two hairpins point in different
> directions)?
I second this. For example,
a^\< b_\p
gives explicitly two different directions and thus should
automatically trigger the functionality of \breakDynamicSpan.
However, this is an additional request; \breakDynamicSpan in the
implementation you have written right now is very useful by its own.
Werner
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
