Neil Puttock [Fri, 4 Jul 2008 22:32:09 +0000 (23:32 +0100)]
Fix 524 pitched trill losing accidental.
- check localKeySignature more thoroughly when deciding whether
to print an accidental. This includes checks for alteration and
measure number.
- print accidental if forced.
- move get_bar_number () from accidental-engraver.cc to context.cc
so that pitched-trill-engraver.cc can also use it.
- check secondary note events for `forced-accidental' property and pass to
engraver via trill-span-event if set.
- prevent accidental-engraver.cc setting `forced' property on non-existent
accidentals.
- add regression tests for forced-accidental and consecutive pitched trills.
Joe Neeman [Thu, 3 Jul 2008 17:30:50 +0000 (20:30 +0300)]
Fix 624.
Remove rhythmic-head-interface from TrillPitchGroup so that it will
not be included in NoteColumns and thus scripts that center on the
NoteColumn will not be affected. The note head in a TrillPitchGroup
is not exactly rhythmic, anyway.
John Mandereau [Sat, 28 Jun 2008 13:57:40 +0000 (15:57 +0200)]
Merge branch 'master' into lilypond/translation
* master: (32 commits)
Tidy up formatting of markup snippets.
MusicXML: Update musicxml2ly to use the new \tempo text dur=count function
Added regtest for parenthesized metronome marks
Small update from Ralph, big changes by Graham.
GDP Rework NR 3.3.2
Fix docs compilation
Update from Ralph.
Fix version number of regression test
Nits in tutorial
bump version
Minor updates.
Update for expressive.itely
New markup command snippets.
Minor improvement
Use noragged-right
Fix version number in regression test case
Fix version number for conversion rule.
LSR: Update.
markuplines: really fix vertical spacing of lines when using eg. \justify-lines
Add noragged-right fragment option.
...
MusicXML: Update musicxml2ly to use the new \tempo text dur=count function
For parenthesized metronome marks, we can now also use the new
\tempo "" dur=count
function, which produces a parenthesized tempo mark if an empty text is
given.
John Mandereau [Thu, 26 Jun 2008 06:43:39 +0000 (08:43 +0200)]
Merge branch 'master' of /home/lilydev/git/lily/
* 'master' of /home/lilydev/git/lily/:
bump version
Minor updates.
Update for expressive.itely
New markup command snippets.
Minor improvement
Use noragged-right
Fix version number in regression test case
Fix version number for conversion rule.
LSR: Update.
markuplines: really fix vertical spacing of lines when using eg. \justify-lines
Add noragged-right fragment option.
New Feature: Include text in \tempo indications
Minor formatting
reminder
More minor tweaks.
Clarify / fix.
Another final touch.
add small png creation info
Update from Francisco with edits.
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