lilypond-user
[Top][All Lists]
Advanced

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

Re: Break_Align_Order


From: Mats Bengtsson
Subject: Re: Break_Align_Order
Date: Fri, 14 Mar 2003 16:30:50 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

David Bobroff wrote:
Mats,

Following your advice I checked the internals page and found this:

breakAlignOrder (list): Defines the order in which prefatory matter (clefs, key signatures)
appears, eg. this puts the key signatures after the bar lines:
\property Score.breakAlignOrder = #'(
                  span-bar
                  breathing-sign
                  clef
                  staff-bar
                  key
                  time-signature
                )

This appeared to be what I needed, ready-made.  I pasted it into my Lily
source and it did put the key changes after the barlines.  Some other
things happened, too.  The clefs and key signatures at the beginnings of
lines don't have staff lines running through them.  They appear to be
pushed to the left.  Also, at the right ends of the lines the staff lines
extend to the right of the barline.  This also produced a lot of errors:

No spacing entry from BarLine/TimeSignature/KeySignature to
`left-edge'/`key-signature'/`left-edge

The example is not really complete. You should start from the current
default setting and just move the objects that you want to move.
According to the documentation, the default is
(instrument-name
 left-edge
 ambitus
 span-bar
 breathing-sign
 clef
 key-signature
 staff-bar
 time-signature
 custos)

If you want to move the key signature after the bar line, you should
use (untested):
(instrument-name
 left-edge
 ambitus
 span-bar
 breathing-sign
 clef
 staff-bar
 key-signature
 time-signature
 custos)

The documentation should be updated.

As for changing the multimeasure behavior; I have read the page linked me
to but I don't know what the syntax is.  Is there a set of instructions for
how this is to be used?

Certainly, read the "Fine tuning a piece" section in the Tutorial and
the "Tuning output" section in the Reference Manual.
For your example, something like
\property Score.MultiMeasureRest \override #'expand-limit = #9
should work.

Another oddity.  I was using:

\mark 1
\mark \default

etc. to put in rehearsal marks.  When it got to "10" it did not print a
"10" but rather a ":", for "11" I got ";" and for "12" I got an inverted
"!".  It is actually a little quicker to type in the numbers but this
seemed to be a bug.

Indeed!

   /Mats






reply via email to

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