
lilypond - issue #2924
Doc: \startMeasureCount and \stopMeasureCount needs documenting
Rietveld for command is here:
https://codereview.appspot.com/6730044/
This patch allows the user to number groups of successive measures, which is useful as an aid to the performer in keeping track of repetitions. There is no requirement that the counted measures be repeated, however. The number is centered on the measure (discounting prefatory material), above the staff by default.
A new grob, a spanner called MeasureCounter,' is created. Each element of
a count is an independent instance of this grob. A new event-class,
measure-
counter-event,' is also defined.
At present, the engraver, Measure_counter_engraver,' must be added
to the relevant context (probably Staff) in the .ly file. This engraver
has been written in Scheme, following the precedent of
Span_stem_engraver.'
The user uses the commands \startMeasureCount' and
\stopMeasureCount'
to frame the measures to count. The initial number is read from a
new grob-property, 'count-from, which may be overridden.
Comment #1
Posted on Mar 17, 2013 by Quick BirdIssue 2924: Doc: \startMeasureCount and \stopMeasureCount needs documenting
The following patch is a preliminary step towards documenting the Measure_counter_engraver added in version 2.17.7. The patch consists of two snippets, the first illustrating basic usage, and the second demonstrating a workaround for creating centered bar numbers.
Comment #2
Posted on Mar 17, 2013 by Quick KangarooPatchy the autobot says: passes make, make test and a full make doc.
Comment #3
Posted on Mar 20, 2013 by Quick KangarooPatch on countdown for 23 March - 12:00 GMT
Comment #4
Posted on Mar 23, 2013 by Quick KangarooPatch counted down - please push
Comment #5
Posted on Mar 23, 2013 by Quick Kangarooauthor David Nalesnik Sat, 16 Mar 2013 16:35:55 +0000 (11:35 -0500) committer James Lowe Sat, 23 Mar 2013 19:44:01 +0000 (19:44 +0000) commit 4d9770a67176122b9779426cf540ad1694f07f61
Comment #6
Posted on Mar 25, 2013 by Quick BirdJames--
Should I close this issue? Perhaps it should be kept open until full documentation is available (NR)?
Comment #7
Posted on Mar 25, 2013 by Quick LionThe issue is already marked "Fixed". You might want to close the Rietveld review. Make a new issue for whatever you consider missing.
Comment #8
Posted on Mar 31, 2013 by Massive Bear(No comment was entered for this change.)
Status: Verified
Labels:
Type-Documentation
Fixed_2_17_15