X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;ds=sidebyside;f=Documentation%2Fnotation%2Fchanging-defaults.itely;h=70ffece67ecc5ee67b01ce3e6d866f78420f5457;hb=c39d188d28fdc84cef8cbaea7b8d6e2fb718c30f;hp=cb8edf2c033a272ccf7aff8124f6a4080e76e343;hpb=5385d029e3e4e89c1a7dba20d3e136f594321816;p=lilypond.git diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely index cb8edf2c03..70ffece67e 100644 --- a/Documentation/notation/changing-defaults.itely +++ b/Documentation/notation/changing-defaults.itely @@ -8,7 +8,7 @@ Guide, node Updating translation committishes.. @end ignore -@c \version "2.17.30" +@c \version "2.19.7" @node Changing defaults @chapter Changing defaults @@ -1342,33 +1342,42 @@ list will be repositioned below the outer context rather than nested within it. The @qq{accepts} list of a context can be changed with the -@code{\accepts} and @code{\denies} commands. @code{\accepts} adds a +@code{\accepts} or @code{\denies} commands. @code{\accepts} adds a context to the @qq{accepts} list and @code{\denies} removes a context -from the list. For example, it would not normally be desirable for -chord names to be nested within a @code{Staff} context, so the -@code{ChordNames} context is not included by default in the @qq{accepts} -list of the @code{Staff} context, but if this were to be required it can -be done: +from the list. + +For example, a square-braced staff group is not usually found within a +curved-braced staff with connecting staff bars, and a @code{GrandStaff} +does not accept a @code{StaffGroup} inside it by default. @lilypond[verbatim,quote] \score { - \new Staff { - c' d' e' f' - \chords { d1:m7 b1:min7.5- } - } + \new GrandStaff << + \new StaffGroup << + \new Staff { c'1 } + \new Staff { d'1 } + >> + \new Staff { \set Staff.instrumentName = bottom f'1 } + >> } @end lilypond +However, by using the @code{\accepts} command, @code{StaffGroup} can be +added to the @code{GrandStaff} context: + @lilypond[verbatim,quote] \score { - \new Staff { - c' d' e' f' - \chords { d1:m7 b1:min7.5- } - } + \new GrandStaff << + \new StaffGroup << + \new Staff { c'1 } + \new Staff { d'1 } + >> + \new Staff { \set Staff.instrumentName = bottom f'1 } + >> \layout { \context { - \Staff - \accepts "ChordNames" + \GrandStaff + \accepts "StaffGroup" } } } @@ -1930,7 +1939,7 @@ the @code{#}@tie{}character. Contexts properties are usually named in @code{studlyCaps}. They mostly control the translation from -music to notation, e.g. @code{localKeySignature} (for determining +music to notation, e.g. @code{localAlterations} (for determining whether to print accidentals), or @code{measurePosition} (for determining when to print a bar line). Context properties can change value over time while interpreting a piece of music; @@ -2564,7 +2573,7 @@ values. Unless this is the intended result, it is safer to update key-values individually with a nested declaration. @warning{Nested declarations will not work for context property -alists (such as @code{beamExceptions}, @code{keySignature}, +alists (such as @code{beamExceptions}, @code{keyAlterations}, @code{timeSignatureSettings}, etc.). These properties can only be modified by completely re-defining them as alists.} @@ -4193,7 +4202,7 @@ and @code{\tieDown} would not help. @lilypond[verbatim,quote,relative=1] << - { e1~ e } + { e1~ 1 } \\ { r4 } >> @@ -4235,7 +4244,7 @@ form of @code{\shape}, this will raise the tie by half a staff-space: << { \shape #'((0 . 0.5) (0 . 0.5) (0 . 0.5) (0 . 0.5)) Tie - e1~ e + e1~ 1 } \\ { r4 }