2008/11/30 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> So, here's the patch:
> http://codereview.appspot.com/8686
>
> Any idea if this is the correct way to solve the problem that you have to
> enter non-standard key signatures in reverse order?
I'm not sure, but it seems to be a harmless change.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 30. November 2008 17:55:19 schrieb Reinhold Kainhofer:
> No, the keyAlterationOrder only affects the generation of the keySignature
> alist from the pitch-alist of the KeyChangeEvent. The
> Key_engraver::read_event function also creates the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 30. November 2008 16:41:14 schrieb Neil Puttock:
> 2008/11/30 Trevor Daniels <[EMAIL PROTECTED]>:
> > I've added a suitable comment to the snippet.
>
> I'm afraid it's not necessarily the case that they'll always be in
> reverse order, sinc
2008/11/30 Trevor Daniels <[EMAIL PROTECTED]>:
> I've added a suitable comment to the snippet.
I'm afraid it's not necessarily the case that they'll always be in
reverse order, since the ordering is controlled by keyAlterationOrder
(which obviously defaults to standard classical ordering).
Regar
Reinhold Kainhofer wrote Sunday, November 30, 2008 3:02 PM
The documentation of the non-standard key signature feature (in the
selected
snippets section of the Key Signatures section) gives an example of such a
key:
http://kainhofer.com/~lilypond/Documentation/user/lilypond/Displaying-
pitche
