[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 279 in project lilypond
From: |
codesite-noreply |
Subject: |
Issue 279 in project lilypond |
Date: |
Tue, 06 Feb 2007 12:44:40 -0800 |
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 TupletBracket #'bracket-visibility = ##t to the last example in the
attached .png). It seems that the TupletBracket is treating the last stem as if
it
belongs to the lower staff. I think the problem might be related to
tuplet-bracket.cc:545 and 546 -- the tuplet positions are based on the
stem-end-positions which don't take into account which staff the stem is on.
But
I'm obviously not understanding something because I don't see how this worked
before. Any ideas?
Attachments:
test.preview.png 2.9 KB
Issue attribute updates:
Status: Started
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 279 in project lilypond, codesite-noreply, 2007/02/05
- Issue 279 in project lilypond, codesite-noreply, 2007/02/06
- Issue 279 in project lilypond,
codesite-noreply <=
- Issue 279 in project lilypond, codesite-noreply, 2007/02/06
- Issue 279 in project lilypond, codesite-noreply, 2007/02/07
- Issue 279 in project lilypond, codesite-noreply, 2007/02/11
- Issue 279 in project lilypond, codesite-noreply, 2007/02/13
- Issue 279 in project lilypond, codesite-noreply, 2007/02/13
- Issue 279 in project lilypond, codesite-noreply, 2007/02/19
- Issue 279 in project lilypond, codesite-noreply, 2007/02/20
- Issue 279 in project lilypond, codesite-noreply, 2007/02/26