| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | Fix #1205....Reinstate an event for \tempo, instead of relying on context property changes.
* input/regression/metronome-range.ly, metronome-text.ly:
replace explicit tempo changes using context props with exported events
* lily/metronome-engraver.cc:
listen to TempoChangeEvent; set as cause for MetronomeMark; pass to metronomeMarkFormatter
proc instead of explicit text, duration and count
* lily/parser.yy (tempo_event):
simplify rule; use single constructor for all types
* scm/define-context-properties.scm (all-user-translation-properties):
emend metronomeMarkFormatter description
remove tempoUnitCount, tempoUnitDuration and tempoText definitions
* scm/define-event-classes.scm (event-classes):
add tempo-change-event
* scm/define-music-display-methods.scm:
rework display method for \tempo
* scm/define-music-properties.scm (all-music-properties):
change type predicate for 'metronome-count
* scm/define-music-types.scm (music-descriptions):
add TempoChangeEvent definition
* scm/ly-syntax-constructors.scm:
rework `tempo' constructor; use for all \tempo styles
remove `tempoText'
* scm/song.scm (tempo->beats):
extract tempo from TempoChangeEvent
* scm/translation-functions.scm (format-metronome-markup):
read tempo properties from event instead of passing as separate args
| Neil Puttock | 2011-02-09 | 1 | -17/+19 |
| * | Regtests: Correct metronome-text.ly docstring....Thanks to Phil Holmes for the report.
| Neil Puttock | 2010-06-10 | 1 | -2/+3 |
| * | Update .ly files. | Neil Puttock | 2008-12-24 | 1 | -1/+1 |
| * | Fix the no note and text in metronome marks; also add regtest | Reinhold Kainhofer | 2008-10-06 | 1 | -0/+2 |
| * | Fix #691: setting \tempo without duration shouldn't print a duration...We can turn off the printing of (dur=count) by simply unsetting the count and duration properties (they are unset in the beginning, so I don't think this will break anything, but then, I'm not totally sure...)
Also added a show regtest for this case.
| Reinhold Kainhofer | 2008-10-06 | 1 | -1/+3 |
| * | Run convert-ly on input/lsr and input/regression | Carl Sorensen | 2008-07-05 | 1 | -1/+1 |
| * | Fix version number in regression test case | Reinhold Kainhofer | 2008-06-24 | 1 | -1/+1 |
| * | New Feature: Include text in \tempo indications...A tempo indication in general is either a text markup, a note=count or both.
So far, lilypond only supported the note=count type of tempo indications in
its \tempo command.
This patch extends the \tempo function to include a text string, too. It
allows any of the following types of tempo settings:
\tempo 4=120
\tempo "Allegro" 4=120
\tempo "Allegro"
\tempo \markup{\italic \medium "Allegro"}
etc.
What it does:
- Extend the parser to allow the above forms for \tempo
- Add a tempoText property, similar to tempoUnitCount
- Metronome_mark_engraver uses this property and checks whether it has
changed
- Extend the metronomeMarkFormatter to take four arguments (text, duration,
count, context) and print either the text, the note=count or text
(note=count), depending on whether the properties are set to sensible
values.
- Add a tempoHideNote property to hide note=count in the metronome mark
- Extend the define-extra-display-method to also check for tempoText and
produce any of the allowed \tempo forms when you use \displayLilyMusic
- Added a convert-ly rule to warn the user about the change to the signature
of the metronomeMarkFormater function
| Reinhold Kainhofer | 2008-06-23 | 1 | -0/+35 |
