Re: [Lilypond-auto] Issue 3247 in lilypond: Patch: Prohibit non-postevents from music functions to be used as post-event

[lilypond]

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

Comment #6 on issue 3247 by address@hidden: Patch: Prohibit non-postevents  
from music functions to be used as post-event
http://code.google.com/p/lilypond/issues/detail?id=3247

Had addressed that comment already.  Pushed to staging as
commit be1247a9a2f9884f4c6b92bb6b637917a544a951
Author: David Kastrup <address@hidden>
Date:   Sat Mar 16 11:22:27 2013 +0100

    Issue 3247: Prohibit non-postevents returned by music functions to be  
used as post-events

    For example,

    { c-\mark \default }

    produced an invalid music expression more or less indistinguishable from

    { \mark \default c }

    Worse is that things like

    { c-\tweak color #red { g } }

    also got accepted.  While \tweak (and other music functions) may
    indeed return either post-events or straight music expressions, there
    should be checks in place that the usage corresponds to its type.

commit 9bba8cec6d52d276f45cd5c9a996fb237e518487
Author: David Kastrup <address@hidden>
Date:   Sat Mar 16 12:10:36 2013 +0100

    Make \balloonText into post-event, \balloonGrobText into proper event

    This is a stopgap measure for getting some consistency into music
    function use.  The real fix would be to convert \ballonText and
    \balloonGrobText to the same kind of interface that \footnote uses.
    Indeed, it might be saner to retire the whole AnnotateOutputEvent
    folderol and instead just use footnotes without footnote-text.


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