oops--forgot to change the version statement back to 2.16.2.
--David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
On Tue, Jul 9, 2013 at 4:05 PM, David Nalesnik wrote:
>
>
> I've got a newer version of this which allows you to make adjustments to
> the position of the tuplet number along the beam from the default centered
> position. (This sometimes proves necessary when there's a collision.)
> I'll look aro
2013/7/9 David Nalesnik :
> Too much clutter on this computer.
I know _exactly_ what your're talking about.
:D
-Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi,
On Tue, Jul 9, 2013 at 3:58 PM, Thomas Morley wrote:
> 2013/7/9 Karol Majewski :
> > Hi
> >
> > Quite some time ago David Nalesnik wrote this amazing function:
> >
> > http://lsr.dsi.unimi.it/LSR/Snippet?id=646
> >
> > The problem is that when I apply it to a staff with
> >
> > {
> > fontSi
2013/7/9 Karol Majewski :
> Hi
>
> Quite some time ago David Nalesnik wrote this amazing function:
>
> http://lsr.dsi.unimi.it/LSR/Snippet?id=646
>
> The problem is that when I apply it to a staff with
>
> {
> fontSize = #-3
> \override StaffSymbol #'staff-space = #(magstep -3)
> }
>
> ... the
Hi
Quite some time ago David Nalesnik wrote this amazing function:
http://lsr.dsi.unimi.it/LSR/Snippet?id=646
The problem is that when I apply it to a staff with
{
fontSize = #-3
\override StaffSymbol #'staff-space = #(magstep -3)
}
... the tuplet numbers are still missplaced. My scheme pr
