From 91daad42eaa0cd330af5c908ac53fbc580bc392b Mon Sep 17 00:00:00 2001 From: David Kastrup Date: Mon, 8 Apr 2013 11:41:22 +0200 Subject: [PATCH] Issue 3303: Add some more documentation for \defaultchild --- .../notation/changing-defaults.itely | 20 ++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely index 09cf63b5c0..443329dfc5 100644 --- a/Documentation/notation/changing-defaults.itely +++ b/Documentation/notation/changing-defaults.itely @@ -1313,9 +1313,23 @@ another, but the required nesting differs. For example, the with the @code{VaticanaVoice} context substituted for the @code{Voice} context in the @qq{accepts} list. -Note that a context will be silently created implicitly if a command -is encountered when there is no suitable context available to -contain it. This can give rise to unexpected new staves or scores. +@cindex contexts, implicit +@cindex implicit contexts +@funindex \defaultchild + +Note that a context will be silently created implicitly if a +command is encountered when there is no suitable context available +to contain it. + +Within a context definition, the type of subcontext to be +implicitly created is specified using @code{\defaultchild}. A +number of music events require a @samp{Bottom} context: when such +an event is encountered, subcontexts are created recursively until +reaching a context with no @samp{defaultchild} setting. + +Implicit context creation can at times give rise to unexpected new +staves or scores. Using @code{\new} to create contexts explicitly +avoids those problems. @cindex alignAboveContext @cindex alignBelowContext -- 2.39.5