Comment #11 on issue 2259 by prze...@gmail.com: Hairpin still hits barline at line break
http://code.google.com/p/lilypond/issues/detail?id=2259
It's counter-intuitive then, because broken-bound-padding's name suggests it should kick in always whenever padding is applied for broken hairpin. If it's not that and there won't be any will to fix it, then I think it should be renamed (broken-collision-bound-padding?).
If padding would be always there (independently of span bar vs bar existence, whether there is collision or not), then maybe would be no need for special behavior of concurrent hairpins (that spanned across same notes should have obviously same horizontal position and length).
IMO defaults should be the most universal settings and at the same time giving same look for similar use-cases (like hairpin below span bar vs one potentially colliding with span bar). Good clean look is possibly top priority for LilyPond, even if it makes code more complex, but if you'll remember my previous sentence, I think that complexity will be be actually lowered.
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
