[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Chord changes over repeat alternatives

From: Yitz Gale
Subject: Re: Chord changes over repeat alternatives
Date: Sun, 20 Aug 2006 08:27:46 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Graham Percival wrote:
> ...lilypond acts according to the docs,

Certainly true.

> so it's not an official "bug".

There is a flaw in the way the feature works that
prevents it from providing its intended functionality
in many cases. In all of the projects I have worked
on over the years, that is considered a bug and
not a feature request.

Unless there is some major issue in the system
design that prevents providing that functionality.
That is what Paul was saying at the beginning of
the thread, because he thought I meant we need to
save the previous state of the engraver across all
of the repeat alternatives.

But that is not the case here. So it should be
classified as a bug.

> ...once the new bug system is running...

Ooo, great news! Good luck with that.

> ...this isn't the most important problem right now.  :)

I have no doubt. But, as far as I can see, this one
shouldn't be too hard to fix.

Thanks to everyone for excellent work on an
excellent app.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]