On Jan 21, 2012, at 11:02 PM, janek.lilyp...@gmail.com wrote:
> So the problem was that by default tupletBracket doesn't have
> outside-staff-priority (because we want it to be placed on staff lines
> sometimes), and the code failed to check for that?
>
> But i don't see how this patch solved the same problem with
> outside-staff-priority set to something:
>
> { % this produced wrong output in 2.15.26, but now is ok:
> \override TupletBracket #'outside-staff-priority = #3
> \times 2/3 {c''4\ff c'' c''}
> }
>
> could you explain?
>
The idea is that if outside-staff-priority is set for either the tuplet-bracket
or the dynamics, their vertical spacing with respect to each other should be
out of the hands of tuplet-bracket.cc and in the hands of the
axis-group-interface.cc .
Cheers,
MS
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
