Updates:
Labels: -Patch-review Patch-needs_work
Comment #6 on issue 509 by colinpkc...@gmail.com: collision nested tuplet
numbers
http://code.google.com/p/lilypond/issues/detail?id=509
Mike Solomon on Rietveld:
Sorry to not have pushed this yet, but I recently rebased this against
current
master and it looks like my stem work actually fixed a good deal of what
some of
this patch was fixing. I've gotten rid of about half the code from this
patch
and posted a new version.
For now, this is just a sketch - it passes regtests, but it does not allow
for
some of the fine tuning that was in the previous patch (tuplet numbers now
push
tuplet brackets much higher than they used to, invalidating the need for all
that skyline stuff from previous patches, thus the deletions). I'm not
sure yet
why this fine tuning doesn't happen, but I'll figure it out in a couple
weeks.
In any case, moxy nested tuplets won't be part of LilyPond for at least
another
month, 3-4 weeks, but when they are, they'll be fully integrated with the
new
Stem work.
Cheers,
MS
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
