|
From: | David Nalesnik |
Subject: | tuplet number on cross-staff kneed-beam |
Date: | Mon, 4 Jul 2011 16:10:12 -0500 |
Hello, all -- First of all, I hope that I'm asking this question on the appropriate list! I'm trying to simplify the workaround relating to tuplet-number position on kneed beams http://lsr.dsi.unimi.it/LSR/Snippet?id=646 and I'm running into an unexpected problem. My reasoning is that, since the tuplet number is positioned according to the bracket, a logical first (certainly hacky!) step is to move the (invisible) bracket to the beam by setting the 'positions property of the bracket to that of the beam. Then, the position of the number could be refined according to its height, the thickness of the beam, etc. This works as planned, except that in 2.14.1, the staves are pushed apart dramatically. \override Beam #'collision-voice-only has no effect on the problem. Manually setting Beam #'positions can be used to fix the problem, but that is obviously inconvenient. I've attached an .ly file with the function (stripped down to fit just this case), and several images of the output (one is produced with 2.12.3, the other two with 2.14.1 -- one with an override of the Beam #'positions). There doesn't appear to be any problem in 2.12.3. Is there anything I can do to fix this problem with the function? Any help would be greatly appreciated! Thanks, David
function-current-stable.png
Description: PNG image
function-current-stable-positions-override.png
Description: PNG image
function-previous-stable.png
Description: PNG image
tuplet-number-function.ly
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |