Updates:
Status: Verified
Comment #14 on issue 573 by v.villenave: score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Okay. Issue 1223 it is.
___
bug-lilypond mailing list
Updates:
Status: Fixed
Owner: ---
Comment #13 on issue 573 by percival.music.ca: score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
This was fixed almost two bloody years ago. The doc issue is a separate
matter, and
Comment #12 on issue 573 by n.puttock: score-final mark mangles score-final
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
I'm now not so sure adding a snippet is the right approach here, since this
seems to
be the same bug as #492 (see my comments in this thread:
Comment #11 on issue 573 by percival.music.ca: score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Valentin said that we needed a new snippet or changing an old one. Neil
said that it
should be a new snippet. I thought this was clear
Comment #10 on issue 573 by frederic...@m4x.org: score-final mark mangles
score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Graham said: I think we just need a few words or a snippet or something to
close this.
Can anybody tell me what to do?
What do we
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #9 by trevorbaca:
OK, thanks Neil. Yup, works!
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #4 by trevorbaca:
Hey Han-Wen,
Unfortunately, looks like running the test case in Valentin's start to the
thread
here in the tracker still causes weirdness (in .57);
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #5 by n.puttock:
Hi Trevor,
You have to unset the new property which Han-Wen added:
\override TupletBracket #'full-length-to-extent = ##f
Regards,
Neil
Attachments:
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #6 by v.villenave:
Yes, indeed.
Issue attribute updates:
Status: Accepted
--
You received this message because you are listed in the owner
or CC fields of this
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #7 by v.villenave:
Hi Neil, you posted your answer at the very same time where I reopened this
issue...
Do we need to set this option as default? Should setting
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #8 by n.puttock:
Oh, I thought you were agreeing with me. ;)
It's set to #t in define-grobs.scm since it would otherwise break
tuplet-full-length.ly, so it's not really
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #3 by v.villenave:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #1 by hanwenn:
Hi,
fixed this by makng the bracket end on the column itself, rather than
the left edge
of the extent (which includes the text.)
Trevor,
does that
Issue 573: score-final mark mangles score-final tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=573
Comment #2 by hanwenn:
whoops, it broke a regtest. I introduced an extra property for this.
--
You received this message because you are listed in the owner
or CC fields of
14 matches
Mail list logo
