Reviewers: Graham Percival, Trevor Daniels, Message: Second Draft
I also just want to check with Reinhold as all I have done here is document the \cueDuringWithClef function (as that is what is in the Reg tests). So is there an explicit \cueClef command that would be used in a different case and should we be bothering to document that or not with an example? http://codereview.appspot.com/4568046/diff/1/Documentation/notation/staff.itely File Documentation/notation/staff.itely (right): http://codereview.appspot.com/4568046/diff/1/Documentation/notation/staff.itely#newcode1285 Documentation/notation/staff.itely:1285: g4. b8 d2 On 2011/06/02 07:10:26, Trevor Daniels wrote:
Restore the R1. A cue is used to indicate when a part should begin playing again, so it is more realistic to show cue notes after a period of resting.
Done. http://codereview.appspot.com/4568046/diff/1/Documentation/notation/staff.itely#newcode1301 Documentation/notation/staff.itely:1301: print the original clef once the cur notes have finished. On 2011/06/02 07:10:26, Trevor Daniels wrote:
cue
Done. http://codereview.appspot.com/4568046/diff/1/Documentation/notation/staff.itely#newcode1309 Documentation/notation/staff.itely:1309: g4. b8 d2 On 2011/06/02 07:10:26, Trevor Daniels wrote:
R1
Done. Description: Doc: NR 1.6.3 Added cueDuringWithClef and cueClef Documented how to use cueDuringWithClef Tracker issue 1658 Also updated some of the original examples to differentiate between strings used for music and those used for the variables in order to make the examples clearer Added appropriate @funindex Also moved \killcues to the end as it seemed more appropriate to have 'how to create all the cue stuff' first and then how to 'kill' them at the end. Also added an @knownissue about making sure that certain arguments are in the correct order. Please review this at http://codereview.appspot.com/4568046/ Affected files: M Documentation/notation/staff.itely _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
