Re: fret-diagrams.scm:657:42: Wrong type: #f

2015-08-19 Thread ClausRogge
Well, your code is not a minimal example and it does not compile and thus it does not show the error. All I can say for now: I suspect your linebreaking of the strings for the fret-diagram. Hi Harm, thanks for replying ... what is "a minimal example"? Anything I can do to make things easier ...

Re: sharping naturals

2015-08-19 Thread David Raleigh Arnold
On Mon, 10 Aug 2015 14:36:41 +0200 Peter Bjuhr wrote: > > When you use key signatures like A major or B Major you end > > up with a lot of naturals in the score for which you may > > have to manually add sharps. > > > > Is there a switch that will automatically sharp all the > > naturals? > > Da

Re: fret-diagrams.scm:657:42: Wrong type: #f

2015-08-19 Thread Thomas Morley
2015-08-19 17:53 GMT+02:00 ClausRogge : > I have two nearly identical pairs of code files, one calling the other. One > of them works, the other one gives me the strange error quoted. > Layout file one: > > %%% > > \version "2.18.2" > > \paper {#(set-default-paper-size "a4") > indent = 0 > top-

Naming Substitution Functions - Numbers and Special Characters

2015-08-19 Thread tone
Does anyone have a list of characters that are allowed in substitution functions. I would like to make a list of chord names including fret position. For example, the following name is allowed: g_dom_seven-three = \markup{ \override #'(size . 1.3) \fret-diagram-terse #"x;x;3;4;3;x;" } However,

fret-diagrams.scm:657:42: Wrong type: #f

2015-08-19 Thread ClausRogge
I have two nearly identical pairs of code files, one calling the other. One of them works, the other one gives me the strange error quoted. Layout file one: %%% \version "2.18.2" \paper {#(set-default-paper-size "a4") indent = 0 top-margin = 0\cm left-margin = 1\cm right-margin = 1\cm

Re: Coloring of key signature accidentals based on their pitch

2015-08-19 Thread David Nalesnik
On Tue, Aug 18, 2015 at 5:34 PM, David Nalesnik wrote: > > > Something else I can't explain: the spacing appears to be slightly > different between the default and modified stencils in both files. This > only affects the positioning of naturals: Padding should only be added in > case of an overla

Re: Guitar Chord Chart - Align Fret Diagram with Chord Names and Notes

2015-08-19 Thread tone
An elegant solution would be to define a fretboard with fret numbers on both sides---one of them an invisible (phantom) character. This is beyond my level of expertise. Anyone know how to code this? Here is a /brute force/ solution using "\once\override LyricText #'extra-offset = #'( /x/ . /y/ )

Re: Using SVG backend to implement point-and-click to braille location

2015-08-19 Thread Mario Lang
Mario Lang writes: > This is basically a big thank you to the LilyPond community. > > I am writing software to deal with braille music code. > Recently, I have started to implement a GUI for the functionality > already implemented, based on Qt. My program uses LilyPond to render > visual music n

Re: Coloring of key signature accidentals based on their pitch

2015-08-19 Thread David Kastrup
David Nalesnik writes: > On Tue, Aug 18, 2015 at 3:43 PM, Heikki Junes > wrote: > >> Thanks David! >> >> Yes, it provides the exactly the desired result! >> > > Glad I could help! See the attached for a completed adaptation. > > I wonder if this function would better be defined in Scheme than C

Re: Coloring of key signature accidentals based on their pitch

2015-08-19 Thread Heikki Junes
Thanks David! I adapted the colors and this key-sig-color-by-pitch.ly did exactly the trick I was looking after! That different color by octave is not actually needed, at least by me. I included that in the example, in order to repeat the different color in different octave found in your example

Re: Mutable and immutable

2015-08-19 Thread David Kastrup
Andrew Bernard writes: > Greetings All, > > Since immutable as an adjective applied to an object in most > programming languages, and in normal English usage means unchanging > over time, or unable to be changed, how is it that the value of > immutable objects can then be changed with \override a