[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 01 Mar 2002 14:21:08 +0100
> address@hidden writes:
> > This has two disadvantages;
> > - it looks fairly cryptical if you are unfamiliar to
> > the inner workings of Lilypond
> > - you specify the same behaviour for the whole score.
> > For single exceptions it's easy to add extra accidentals
> > with cis! (forced accidentals) but as far as I know we don't
> > have the opposite alternative, preventing accidentals for
> > a single note. Of course you could also play with Rune's new
> > autoAccidentals property.
> actually, there is another thing. It will undoubtedly lead to more
> collisions. However, accidental formatting is still a weak point of
> lily, so maybe this won't make it worser.
How much would it break the Lilypond architecture to keep the
Accidenal_engraver in the Staff context but making it aware of
which accidental belongs to which voice, so it still could handle
each voice separately if the user requests so in some property?