<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <!-- header_tag --> <html lang="en"> <head> <title>Special considerations - GNU LilyPond Notation Reference</title> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="description" content="GNU LilyPond Notation Reference"> <meta name="generator" content="makeinfo 4.11"> <link title="Top" rel="start" href="index.es.html#Top"> <link rel="up" href="Controlling-visibility-of-objects.es.html#Controlling-visibility-of-objects" title="Controlling visibility of objects"> <link rel="prev" href="Using-break_002dvisibility.es.html#Using-break_002dvisibility" title="Using break-visibility"> <link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage"> <!-- Copyright (C) 1999--2007 by the authors Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections. A copy of the license is included in the section entitled ``GNU Free Documentation License''. --> <meta http-equiv="Content-Style-Type" content="text/css"> <style type="text/css"><!-- pre.display { font-family:inherit } pre.format { font-family:inherit } pre.smalldisplay { font-family:inherit; font-size:smaller } pre.smallformat { font-family:inherit; font-size:smaller } pre.smallexample { font-size:smaller } pre.smalllisp { font-size:smaller } span.sc { font-variant:small-caps } span.roman { font-family:serif; font-weight:normal; } span.sansserif { font-family:sans-serif; font-weight:normal; } hr { border:0; height:1; color: #000000; background-color: #000000; } /* hr { border: none; height: 1px; color: #666666; background-color: #666666; } body { border-left: 1px solid #666666; border-right: 1px solid #666666; color: #332d28; margin-right: auto; margin-left: auto; width: 60em; list-style-type: square; font-family: Arial,Helvetica,sans-serif; padding-right: 1em; padding-left: 1em; } a { border-bottom: 1px dashed #344242; text-decoration: none; color: #344242; } a:link { text-decoration: none; } a:visited { border-bottom: 1px dashed #666666; color: #666666; } a:active { border-bottom: 1px solid #00cccc; color: #00cccc; } a:hover { border-bottom: 1px solid #1d7b85; color: #1d7b85; } blockquote { border: 1px solid #cccccc; padding: 3px; width: 40em; } .node { border-left: 1px solid #666666; margin: -0.5em 0px 1em; padding: 2px 1px 0px; font-style: italic; } .node a { border: none; text-decoration: underline; font-style: normal; font-weight: bold; } .verbatim { font-family: "Courier New",Courier,monospace; } .unnumberedsubsubsec { font-size: large; color: #1d7b85; } .subsubheading { font-size: large; color: #3b220d; } .contents { border: 1px dashed #339999; margin: 3px 2em; list-style-type: square; padding-right: 1em; width: 40em; background-color: #fcfff9; } .contents a { border-bottom: 1px dashed #423d34; text-decoration: none; color: #423d34; } .contents a:visited { border-bottom: 1px dashed #666666; color: #666666; } .contents a:active { border-bottom: 1px solid #f0d86d; color: #f0d86d; } .contents a:hover { border-bottom: 1px solid #3b220d; color: #3b220d; } .menu { border-left: 1px dashed #339999; margin: 3px 2em 1em; list-style-type: square; padding-left: 1.4em; width: 40em; } .unnumbered { } h2 { font-size: x-large; color: #1d7b85; } */ --></style> </head> <BODY BGCOLOR=WHITE TEXT=BLACK> <div class="node"> <p> <a name="Special-considerations"></a> Previous: <a rel="previous" accesskey="p" href="Using-break_002dvisibility.es.html#Using-break_002dvisibility">Using break-visibility</a>, Up: <a rel="up" accesskey="u" href="Controlling-visibility-of-objects.es.html#Controlling-visibility-of-objects">Controlling visibility of objects</a> <hr> </div> <h5 class="unnumberedsubsubsec">Special considerations</h5> <p><em>Visibility following explicit changes</em> <p><a name="index-key-signature_002c-visibility-following-explicit-change-2725"></a><a name="index-explicitKeySignatureVisibility-2726"></a><a name="index-clef_002c-visibility-following-explicit-change-2727"></a><a name="index-explicitClefVisibility-2728"></a> The <code>break-visibility</code> property controls the visibility of key signatures and changes of clef only at the start of lines, i.e. after a break. It has no effect on the visibility of the key signature or clef following an explicit key change or an explicit clef change within or at the end of a line. In the following example the key signature following the explicit change to B-flat major is still visible, even though <code>all-invisible</code> is set. <blockquote> <pre class="verbatim"> \key g \major f4 g a b % Try to remove all key signatures \override Staff.KeySignature #'break-visibility = #all-invisible \key bes \major f4 g a b \break f4 g a b f4 g a b </pre> <p> <a href="../21/lily-e1fe88f8.ly"> <img align="middle" border="0" src="../21/lily-e1fe88f8.png" alt="[image of music]"> </a> </p> </blockquote> <p>The visibility of such explicit key signature and clef changes is controlled by the <code>explicitKeySignatureVisibility</code> and <code>explicitClefVisibility</code> properties. These are the equivalent of the <code>break-visibility</code> property and both take a vector of three booleans or the predefined functions listed above, exactly like <code>break-visibility</code>. Both are properties of the Staff context, not the layout objects themselves, and so they are set using the <code>\set</code> command. Both are set by default to <code>all-visible</code>. These properties control only the visibility of key signatures and clefs resulting from explicit changes and do not affect key signatures and clefs at the beginning of lines; <code>break-visibility</code> must still be overridden in the appropriate object to remove these. <blockquote> <pre class="verbatim"> \key g \major f4 g a b \set Staff.explicitKeySignatureVisibility = #all-invisible \override Staff.KeySignature #'break-visibility = #all-invisible \key bes \major f4 g a b \break f4 g a b f4 g a b </pre> <p> <a href="../44/lily-aa42c546.ly"> <img align="middle" border="0" src="../44/lily-aa42c546.png" alt="[image of music]"> </a> </p> </blockquote> <p><em>Visibility of cautionary accidentals</em> <p>To remove the cautionary accidentals printed at an explicit key change, set the Staff context property <code>printKeyCancellation</code> to <code>#f</code>: <blockquote> <pre class="verbatim"> \key g \major f4 g a b \set Staff.explicitKeySignatureVisibility = #all-invisible \set Staff.printKeyCancellation = ##f \override Staff.KeySignature #'break-visibility = #all-invisible \key bes \major f4 g a b \break f4 g a b f4 g a b </pre> <p> <a href="../25/lily-baa9ea1d.ly"> <img align="middle" border="0" src="../25/lily-baa9ea1d.png" alt="[image of music]"> </a> </p> </blockquote> <p>With these overrides only the accidentals before the notes remain to indicate the change of key. <!-- TODO Add visibility of cautionary accidentals before notes --> <p><em>Automatic bars</em> <p><a name="index-automaticBars-2729"></a><a name="index-bar-lines_002c-suppressing-2730"></a> As a special case, the printing of bar lines can also be turned off by setting the <code>automaticBars</code> property in the Score context. If set to <code>#f</code>, bar lines will not be printed automatically; they must be explicitly created with a <code>\bar</code> command. Unlike the <code>\cadenzaOn</code> predefined command, measures are still counted. Bar generation will resume according to that count if this property is later set to <code>#t</code>. When set to <code>#f</code>, line breaks can occur only at explicit <code>\bar</code> commands. <!-- TODO Add example --> <p><em>Octavated clefs</em> <p><a name="index-octavated-clefs_002c-visibility-of-2731"></a><a name="index-visibility-of-octavated-clefs-2732"></a><a name="index-clefs_002c-visibility-of-octavation-2733"></a> The small octavation symbol on octavated clefs is produced by the <code>OctavateEight</code> layout object. Its visibility is controlled independently from that of the <code>Clef</code> object, so it is necessary to apply any required <code>break-visibility</code> overrides to both the <code>Clef</code> and the <code>OctavateEight</code> layout objects to fully suppress such clef symbols at the start of each line. <p>For explicit clef changes, the <code>explicitClefVisibility</code> property controls both the clef symbol and any octavation symbol associated with it. <p class="noindent"> <h5 class="subsubheading">See also</h5> <p class="indent"> Learning Manual: <a name="index-Visibility-and-color-of-objects-2734"></a><a href="../lilypond-learning/Visibility-and-color-of-objects.es.html#Visibility-and-color-of-objects">Visibility and color of objects</a> <!-- footer_tag --><br><hr> <div class="node"> <p> Previous: <a rel="previous" accesskey="p" href="Using-break_002dvisibility.es.html#Using-break_002dvisibility">Using break-visibility</a>, Up: <a rel="up" accesskey="u" href="Controlling-visibility-of-objects.es.html#Controlling-visibility-of-objects">Controlling visibility of objects</a> </div> <div style="background-color: #e8ffe8; padding: 2; border: #c0ffc0 1px solid;"> <p> <font size="-1"> Esta página corresponde a LilyPond-2.11.57 (rama de desarrollo). <br> <address> Informe de los fallos a través de la lista en español <a href="http://es.groups.yahoo.com/group/lilypond-es/">lilypond-es</a>, o en inglés a través de <a href="http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs">http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs</a>. </address> <br> Se agradecen las <a href="http://lilypond.org/web/devel/participating/documentation-adding">sugerencias para la documentación</a>. </font> </p> </div> </BODY></html>