lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 3296 in lilypond: Patch: Move Tweak_engraver t


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3296 in lilypond: Patch: Move Tweak_engraver to Score level
Date: Tue, 09 Apr 2013 07:22:09 +0000

Updates:
        Status: Fixed
        Labels: -Patch-push Fixed_2_17_16

Comment #5 on issue 3296 by address@hidden: Patch: Move Tweak_engraver to Score level
http://code.google.com/p/lilypond/issues/detail?id=3296

Pushed to staging as
commit 77d99c047772da8e897af75c49b00523556da01e
Author: David Kastrup <address@hidden>
Date:   Thu Apr 4 11:12:38 2013 +0200

    Issue 3296: Move Tweak_engraver to Score level

    This makes it possible to tweak items announced at Score level, like
    MetronomeMark and RehearsalMark.

    The advantage is that tweaks will be applied once regardless of the
    context structure (the Score context should exist only once).

    Due to the hierarchical nature of acknowledgers, acknowledgers in
    lower contexts will now get to see the grobs before tweaks have been
    applied.  However, grobs are still unfinished (except for type,
    properties initialized via context properties and cause) at the time
    they are announced, with other details only getting filled in by the
    engraver after announcement, so the potential for trouble seems low.
    Acknowledgers should usually just register a grob (or write grob data)
    with any actual reading of grob data occurring at the end of the
    timestep instead.


--
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



reply via email to

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