Status: Accepted Owner: v.villenave CC: hanwenn Labels: Type-Enhancement Priority-Low Usability Bounty
New issue 824 by v.villenave: Enhancement: anchors in the music stream http://code.google.com/p/lilypond/issues/detail?id=824 Kieren has sent a very interesting proposal: http://lists.gnu.org/archive/html/lilypond-devel/2009-07/msg00544.html " Like many Lilyponders, I break down my code into variables, e.g. global (for time signature changes, etc.), notes, dynamics, etc. The main irritation with this (IMO) is that each variable requires a complete set of skips in order to keep the timing accurate. Would it be technically feasible/possible to establish a system of "anchors" instead? That is, could we declare an anchor point in the global setup, and then refer to it in other code? e.g. global = { \time 4/4 s4*4*10 \time 3/4 s4*3*5 \time 7/4 s4*7 \time 4/4 \anchor #'coda s4*4*10 \bar "|." } tempoChanges = { \tempo \markup "Opening tempo" \anchorTo #'coda \tempo \markup "Extremely slow" } " Jay has proposed a slightly simpler syntax: " That's a neat idea. It might be easier to do something like: global = { \time 4/4 s4*4*10 \time 3/4 s4*3*5 \time 7/4 s4*7 \time 4/4 \anchor #'coda s4*4*10 \bar "|." } \addAt #'coda \global {\tempo \markup "Extremely slow"} Then the addAt function could weave the tempo in at the correct point. " Han-Wen has offered to help anyone would be willing to implement it: http://lists.gnu.org/archive/html/lilypond-devel/2009-08/msg00102.html " I can imagine how this would be implemented, but it would be a lot of work. If anyone is up for a challenge, I can give some pointers. :) " I suspect many people would pay for such a killer-feature. As always, I am ready to double the fee. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings _______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
