On Fri, Jul 1, 2011 at 1:09 PM, Han-Wen Nienhuys <hanw...@gmail.com> wrote: >> The problem with this is that, in the axis-group-interface, the TupletNumber >> either: >> >> (1) Does not have an outside staff priority and therefore is included in the >> staff's skyline, which pushes the bracket too high. >> (2) Does have an outside staff priority, in which case it may push other >> grobs too high above it (and it would have to be artificially re-placed in >> the correct spot with respect to the TupletBracket).
Wouldnt it be much easier for the tuplet number's extents to be ignored for skyline purposes if there already is an associated tuplet bracket? Practically speaking, the tupletnumber adapts its position to the bracket, so it is best for the implementation to also do this. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
