On Jul 1, 2011, at 6:09 PM, Han-Wen Nienhuys wrote: > On Fri, Jul 1, 2011 at 12:44 PM, m...@apollinemike.com > <m...@apollinemike.com> wrote: >> On Jul 1, 2011, at 5:02 PM, hanw...@gmail.com wrote: >> >>> This patch doesnt make sense to me. The TupletBracket grob is already >>> linked to the TupletNumber. The correct way to fix this is to make sure >>> the number lets the bracket decide its position. >>> >>> >> >> 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). > > maybe I misunderstand the problem. Are you fixing the slope of the > bracket (should be sloped), or the position of the number (not > centered on the bracket?)
The position of the number. Cheers, MS _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
