Re: [Lilypond-auto] Issue 4138 in lilypond: Patch: Make \time work with \tweak and \footnote

[lilypond]

Updates:
        Labels: -Patch-push Fixed_2_19_16

Comment #8 on issue 4138 by address@hidden: Patch: Make \time work with \tweak  
and \footnote
https://code.google.com/p/lilypond/issues/detail?id=4138

Pushed to staging as
commit 78c9194fe61a9cbe372b12ec5125779acf706a77
Author: David Kastrup <address@hidden>
Date:   Sun Sep 28 10:58:43 2014 +0200

    Issue 4138: Make \time work with \tweak and \footnote

    The way this is done is to let a TimeSignatureMusic expression expand to
    produce a TimeSignatureEvent that can be listened to.  The
    Time_signature_engraver _does_ listen to this event and uses it to set
    the origin for TimeSignature grobs created in the same time step.
    Another effect is that any warnings associated with a TimeSignature grob
    will be able to point to a source location in case that the respective
    change of timing parameters can be traced to TimeSignatureMusic in a
    context below the context of the Time_signature_engraver creating the
    TimeSignature.

    Since events that can be listened to create a Bottom context implicitly,
    this causes a difference for cases like

    \score { { \time 3/4 \skip 2. r2. } }

    Previously, Staff (and Voice) contexts were only created _after_ the
    \skip completed (the timing parameters are set in the Timing context,
    equal to Score by default), making the time signature appear only in
    measure 2.  Now the implicit creation of a Staff (and thus a
    Time_signature_engraver) in the course of creating a Bottom context (in
    this case a Voice) makes the time signature appear right away.

    If one uses a separate non-printing context for containing timing info,
    one has to make sure that any implicitly created Bottom context is
    non-printing as well.


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings