[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emproving Documentation about chordGlissando [WAS:consecutive chordG
Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando]
Mon, 25 Apr 2011 11:33:39 -0600
On 4/25/11 11:26 AM, "Federico Bruni" <address@hidden> wrote:
> Il giorno lun, 25/04/2011 alle 00.09 +0200, Federico Bruni ha scritto:
>> Or should I rather edit
> I've changed my mind and I think that I should edit this file instead of
> In the meanwhile I've realized that relative mode triggers another error
> when chordGlissando moves down (from higher to lower pitches). Pitches
> are correct, but glissandi are in a mess.
> See chord-glissando-down.ly attached.
> There's a workaround for this error?
> I think that documentation should cover this issue as well (if there's
> not a workaround, we might say that a chordGlissando "moving back"
> should be entered in absolute mode?).
It looks to me like the proper documentation is a warning that says
"chordGlissando is unreliable in relative mode. It is recommended to be
always used in absolute mode."
A bug report should be posted.
We don't normally list bugs as warnings, so maybe once we list the bug we
can't have the warning.
It appears to me right now that chordGlissando is a sufficiently rough hack
that it should probably be removed from the distribution and just be present
in the LSR.