Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #10 by gpermus: (No comment was entered for this change.) Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of thi

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #9 by joeneeman: Thanks for your patience. This should be fixed in 2.11.20. Issue attribute updates: Status: fixed Labels: fixed_2_11_20 -- You received this message because yo

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #8 by joeneeman: Ah, OK. The minimal example works for me, but the original one doesn't. I'll get back to work on this. Issue attribute updates: Status: started Labels: -fixed_

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #7 by horndude77: Same problem in 2.11.18. Perhaps it's been fixed since? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred th

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #6 by joeneeman: Does it work in 2.11.18? It could be that the changes didn't make it in time for 2.11.17. It certainly looks OK when I run it with git head. Issue attribute updates: L

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #5 by horndude77: The first example doesn't seem to be fixed in 2.11.17. The segfault and the smaller example are both fixed, but the in the original report the beam from the first group of trip

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #4 by joeneeman: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_17 -- You received this message because you are listed in t

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #3 by hanwenn: .14 also fails this, and I suspect it was broken all along. The correct solution is to add stem->relative_coordinate(common_y, Y_AXIS) to left & right Y coordinate. -- Yo

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #2 by joeneeman: I have a partial fix in branch jneeman. It successfuly delays Tuplet_bracket::print until after line breaking, but the tuplet bracket is drawn wrong anyway (I added \override

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 Comment #1 by [EMAIL PROTECTED]: A shorter example of cross-staff tuplet breakage: \version "2.11.16" \paper { ragged-right = ##t } \score { \new PianoStaff << \new Staff = "RH" { s4 } \new S

Issue 279 in project lilypond

Issue 279: x-staff tuplets cause havoc http://code.google.com/p/lilypond/issues/detail?id=279 New issue report by hanwenn: Joe, can you have a look? It seems related to recent piano-staff refactoring. \version "2.11.16" \paper { ragged-right = ##t } spacer = { %% remove this: broken forma