[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Doc: NR Pitches.itely - added 2 new snippets (issue 110240044 by add
From: |
pkx166h |
Subject: |
Re: Doc: NR Pitches.itely - added 2 new snippets (issue 110240044 by address@hidden) |
Date: |
Mon, 30 Jun 2014 21:40:17 +0000 |
Is it worth making the Notation Reference longer?
What do you suggest?
https://codereview.appspot.com/110240044/diff/40001/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):
https://codereview.appspot.com/110240044/diff/40001/Documentation/notation/pitches.itely#newcode1325
Documentation/notation/pitches.itely:1325: \override
Staff.KeySignature.flat-positions = #'((-5 . 5))
On 2014/06/29 03:17:00, Keith wrote:
This already shows how to print key signatures over a different or
wider range
of the staff. You might consider this good enough.
I don't understand what you mean. Good enough compared to what?
https://codereview.appspot.com/110240044/diff/40001/Documentation/snippets/new/creating-custom-key-signatures.ly
File Documentation/snippets/new/creating-custom-key-signatures.ly
(right):
https://codereview.appspot.com/110240044/diff/40001/Documentation/snippets/new/creating-custom-key-signatures.ly#newcode26
Documentation/snippets/new/creating-custom-key-signatures.ly:26:
\musicglyph #"clefs.F"
On 2014/06/29 03:17:00, Keith wrote:
But F is not 3 staff-spaces below C, only 2.
You could \translate #'(-3 . -2) \musicglyph #"clefs.F" to avoid the
overlap.
Or you could use a G clef \translate #'(0. +2) \musicglyph #"clefs.G"
Thanks, I went for the 'avoiding overlap'.
https://codereview.appspot.com/110240044/