> padding (for TupletNumber) only comes into effect for Y-offset when
> considering kneed beams:
>
>
> \version "2.19.82"
> {
> \tuplet 5/2 { b8[ b'' b b'' b] }
> \once \override TupletNumber.padding = #1
> \tuplet 5/2 { b8[ b'' b b'' b] }
> }
>
>
> Otherwise, the computation is
On 2019-04-01 1:16 pm, Werner LEMBERG wrote:
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is apparently completely undoc
>> if I use `\magnifyStaff', the tuplet number is too far away from
>> the beam. How can I move it nearer to the beam? Looking into
>> `tuplet-number.cc' I see a `padding' property with a default value
>> of 0.5 (and which is apparently completely undocumented).
>
> There's a few ways to pad ou
On 4/1/2019 4:16 PM, Werner LEMBERG wrote:
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is apparently completely undocum
Folks,
if I use `\magnifyStaff', the tuplet number is too far away from the
beam. How can I move it nearer to the beam? Looking into
`tuplet-number.cc' I see a `padding' property with a default value of
0.5 (and which is apparently completely undocumented). However, doing
something like
\o
