|
From: | lilypond |
Subject: | Re: [Lilypond-auto] Issue 2397 in lilypond: Tuplet number incorrectly placed when using additonal articulations and/or abreak |
Date: | Sat, 02 Jun 2012 22:06:27 +0000 |
Comment #17 on issue 2397 by address@hidden: Tuplet number incorrectly placed when using additonal articulations and/or abreak
http://code.google.com/p/lilypond/issues/detail?id=2397 Not much of a surprise here. 26d40794616f7dc6d47af25bb373a5d2353633cf is the first bad commit commit 26d40794616f7dc6d47af25bb373a5d2353633cf Author: Mike Solomon <address@hidden> Date: Wed Dec 28 09:50:18 2011 +0100 TupletBracket and TupletNumber avoid Script by default. This can be turned off by setting avoid-scripts to ##f. Scripts are placed in a "scripts" grob array in the tuplet-engraver and are then accessed in tuplet-bracket.cc and treated as items to encompass when calculating a bracket's vertical position.:040000 040000 075a3e1910de58b2b5565b52ba13693d1c2fc69f 18c7e3f4bf129825381496a3c7250f8894f41f78 M input :040000 040000 158544785deeaced3ea98e0247f05547955b95d4 913f0853b908307c8f5ba050305cd38e90aef9fb M lily :040000 040000 9756fb0face9dbc99d9eab8751148fb3ac8e4a91 b8bb677cf1a753ba8380bb60a9df553029207d64 M scm
[Prev in Thread] | Current Thread | [Next in Thread] |