On Thu, Dec 06, 2012 at 11:17:57AM +0100, Mike Solomon wrote: > On 6 d?c. 2012, at 11:08, Colin Hall <[email protected]> wrote: > > > > > Hi, > > > > I'm handling a feature request on bug-lilypond for some enhancements > > to the fret diagram features. > > > > http://lists.gnu.org/archive/html/bug-lilypond/2012-12/msg00002.html > > > > I don't think the new functionality has been adequately defined by > > those who requested it. > > > > Could one or more of the devs advise me on whether to accept the > > request, reject it, or press for further definition? > > > > If you think a request for further definition is the correct response, > > please be specific about what is missing. > > > > > > Cheers, > > Colin. > > The easiest thing to do would be to create a context property that > is a list of alists, where each alist corresponds to a string from > low to high. So, for example, for a two-string instrument, > something like : > > \set fretMarkProperties = #'(((color . red) (type . letters) > (upsidedown . #f)) ((color . blue) (type . numbers))) > > This can include whatever parameters make sense and can be fed to > the fret diagram constructor. After this is implemented, wrapper > functions can do what this person is talking about (i.e. a Scheme > function that identifies roots/thirds/fifths and then composes the > list of alists accordingly). > > So as a request, I'd put "Implement customizable fret-diagram mark > properties" or something of the like. How the customizations are > used is up to the user. >
Thanks, Mike, the prompt advice is appreciated. Looks like this is tractable. I'll create a tracker and acknowledge the report. Cheers, Colin. -- Colin Hall _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
