lilypond-devel
[Top][All Lists]
Advanced

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

Re: Doc: Pitches.itely @knownissue OctavateEight grob (issue 6761045)


From: pkx166h
Subject: Re: Doc: Pitches.itely @knownissue OctavateEight grob (issue 6761045)
Date: Wed, 24 Oct 2012 15:18:26 +0000

Reviewers: Trevor Daniels,

Message:
On 2012/10/24 14:57:28, Trevor Daniels wrote:
LGTM, but just a thought - might it be better
to override the colour so the change results in
something visible rather than just an absence of
the clef?
Trevor

Good idea.

Next patch on its way.

James

Description:
Doc: Pitches.itely @knownissue OctavateEight grob

Issue 2832

Shows that any integers attached to a Clef is treated as a separate Grob
so any override applied to the Clef also has to be applied
as a separate override to the OctavateEight grob.

Includes brief description and @lilypond example.

Please review this at https://codereview.appspot.com/6761045/

Affected files:
  M Documentation/notation/pitches.itely


Index: Documentation/notation/pitches.itely
diff --git a/Documentation/notation/pitches.itely b/Documentation/notation/pitches.itely index 860babdc821d081bef8a96ed4042c699f1fc4683..3b7ca08ce8ec83c5cc8282e616a7e1f2de92b940 100644
--- a/Documentation/notation/pitches.itely
+++ b/Documentation/notation/pitches.itely
@@ -1179,6 +1179,21 @@ Internals Reference:
 @rinternals{OctavateEight},
 @rinternals{clef-interface}.

address@hidden
+Any integers that are attached to clefs are treated as separate grobs,
+so any @code{\override} done to the @var{Clef} will also need to be
+applied, as a separate @code{\override}, to the @var{OctavateEight}
+grob.
+
address@hidden,quote,relative=1]
+\new Staff \with {
+  \override OctavateEight #'transparent = ##t
+  \override Clef #'transparent = ##t
+}
+
+\clef "treble_8" c4
address@hidden lilypond
+

 @node Key signature
 @unnumberedsubsubsec Key signature





reply via email to

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