On Dec 4, 2013, at 9:45 PM, Urs Liska <u...@openlilylib.org> wrote: > Am 04.12.2013 17:15, schrieb Jan-Peter Voigt: >> Am 04.12.2013 17:01, schrieb Urs Liska: >>> My \annotate function should also store the position in the score (to >>> print that out and to sort by it). >>> So when I use the function in the input file it should store location >>> elements and current measure and measure position in several variables. >> so yout need some kind of music function, that inserts an info to the >> music objects, which will be caught by an engraver, or you use applyContext. >> Then you need some kind of singleton, which holds the annotations. Then >> you can add them anywhere and get the list afterwards. >> Later more on that ... >> > > Yes, that's for later. Now I first need to collect information on the current > moment. > > And I _do_ have read the whole section of lalily's edition.scm. But it's > _way_ too complex, in particular because it references so much other code > from outside the file. > IISC it isn't exactly what I need so I'm afraid I have to build up my stuff > from ground up. Also in order to have understood what it does. > > Best > Urs
>From practice, my advice is to create a music function that does all this >bookkeeping for you by iterating through your stream, minding time signatures, >counting durations and adding events when appropriate. All this before it >hits the engravers. I wrote a function that that did this back when I removed >all the Es from the Overture to Fidelio (http://bit.ly/1gEXXJ7), but I lost >the function when my hard drive crashed. It was a day of work, though, so >it’s re-doable and probably very useful for lots of people. Cheers, MS _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
