From 60d8d592c4d182f0143ccfdcc09735fee15c9fbf Mon Sep 17 00:00:00 2001 From: James Lowe Date: Tue, 5 Oct 2010 17:26:22 +0100 Subject: [PATCH] Doc: Added note for users in LM about \new Score Tracker 1033 --- Documentation/learning/fundamental.itely | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/Documentation/learning/fundamental.itely b/Documentation/learning/fundamental.itely index fbd0778c84..d6ec260df8 100644 --- a/Documentation/learning/fundamental.itely +++ b/Documentation/learning/fundamental.itely @@ -1460,16 +1460,12 @@ where @var{type} is a context name (like @code{Staff} or @code{Voice}). This command creates a new context, and starts interpreting the @var{music-expression} within that context. -(Note that a @code{\new Score} command is not normally required, -as the essential top-level @code{Score} context is created -automatically when the music expression within the @code{\score} -block is interpreted. The only reason for creating a @code{Score} -context explicitly using @code{\new Score} is to introduce a -@code{\with} block in which one or more score-wide default values -of context properties may be specified. Information on using -@code{\with} blocks can be found under the heading -@qq{Setting context properties with @code{\\with} } in -@ref{Modifying context properties}.) +@warning{@bs{}@code{new Score} should not be used as the essential +top-level @code{Score} context is created automatically when the music +expression within the @bs{}@code{score} block is interpreted. Score-wide +default values of context properties can be changed within the +@bs{}@code{layout} block. +See @rlearning{Changing all contexts of the same type}} You have seen many practical examples which created new @code{Staff} and @code{Voice} contexts in earlier sections, but -- 2.39.5