On 2020-08-29 5:23 am, David Kastrup wrote:
Wols Lists <[email protected]> writes:
On 29/08/20 05:45, Werner LEMBERG wrote:
\once \override FretBoard.size = #'1.0
\once \override FretBoard.fret-diagram-details.barre-type =
#'straight
\once \override FretBoard.fret-diagram-details.dot-color =
#'black
\once \override FretBoard.fret-diagram-details.finger-code =
#'below-string
c'
Unfortunately this might well require re-writing the parser, but it
struck me it might be a nice idea to nick an idea from other object
oriented languages as follows ...
\once \override FretBoard.size = #'1.0
\once \override \using FretBoard.fret-diagram-details {
.barre-type = #'straight
.dot-color = #'black
.finger-code = #'below-string
}
c'
What's wrong with
\once \override FretBoard.fret-diagram-details =
#'((barre-type . straight)
(dot-color . black)
(finger-code . below-string))
I mean, I am as proud as anybody that separate subproperty overrides
don't cause LilyPond to go down in flames any more, but this is an
alist, after all.
In my testing, that overwrites any existing overrides on the
fret-diagram-details property, so it is not quite the same thing.
-- Aaron Hill
