Re: [Denemo-devel] Change to semantics of Chord Directives prefix field

[Richard Shann]

Actually, we have these:

actions/menus/ObjectMenu/NotesRests/RestEntry/MultiMeasureRests:
(d-DirectivePut-chord-prefix "WholeMeasureRest" "%{")
actions/menus/ObjectMenu/NotesRests/RestEntry/WholeMeasureRest:
(d-DirectivePut-chord-prefix "WholeMeasureRest" (string-append "R1*"
timesig " %{"))
actions/menus/ObjectMenu/NotesRests/RestEntry/WholeMeasureRest:
(d-DirectivePut-chord-prefix "WholeMeasureRest" (string-append "R1*"
timesig " %{"))

actions/menus/ObjectMenu/ChordMenu/Markings/Metronome
Markings/MetronomeMarking:(d-DirectivePut-chord-prefix
"MM" (string-append "\\override Score.MetronomeMark #'padding = #3
actions/menus/ObjectMenu/ChordMenu/Markings/TextMarks/ParenthesizeChord:(d-DirectivePut-chord-prefix
 "Parenthesize" "\\parenthesize ")

The last of these is simply a mistake - it parenthesizes the wrong
chord. The rest ones are what we will be replacing with the new duration
setting code; only the "MM" one needs looking at...

Richard


On Thu, 2010-10-14 at 18:10 +0100, Richard Shann wrote:
> At the moment the prefix field in a directive attached to a chord is
> emitted in the LilyPond output before the chord. This is of no
> particular use (a standalone directive could do this anyway). We do
> however have currently no way to prefix the duration of a chord (which
> we would need to do to replace it with \lunga etc).
> So I propose to change the meaning of the prefix field for that type of
> directive.
> It is unlikely this field has been used by anyone, as LilyPond long ago
> went postfix.
> Any objections?
> Richard
> 
> 
> 
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/denemo-devel