On 2013/03/09 07:18:50, mike7 wrote:
On 8 mars 2013, at 14:10, mailto:d...@gnu.org wrote:
> >
https://codereview.appspot.com/7453046/diff/1/input/regression/minimum-length-end-line.ly
> File input/regression/minimum-length-end-line.ly (right): > >
https://codereview.appspot.com/7453046/diff/1/input/regression/minimum-length-end-line.ly#newcode10
> input/regression/minimum-length-end-line.ly:10: \override > TextSpanner.springs-and-rods = #ly:spanner::set-spacing-rods > Why is this override needed for the regtest? The other overrides
are
> obvious user-accessible overrides for triggering the tested > functionality. > > But should _this_ override not be the default? > > https://codereview.appspot.com/7453046/
Perhaps open a tracker issue for this? The question is not only valid for text spanners but also hairpins,
glissandos,
etc.
Last time I looked, this issue purportedly "Allows minimum-length to work for end-of-line spanners." And according to the regtest, it does not do the job. Without additional messing with springs-and-rods it does not allow minimum-length to work for end-of-line-spanners. The only thing more frustrating than missing functionality is purportedly available functionality that needs non-user-comprehensible trickery to actually work. Please don't turn LilyPond into a secret bag of tricks only for the initiated. It is emasculating its users. Separately problematic is that the secret interface contains \override TextSpanner.springs-and-rods = #ly:spanner::set-spacing-rods which apparently should be the default but is only tested in a single regtest. So it is not clear that using this functionality would not break other things elsewhere. https://codereview.appspot.com/7453046/ _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
