Urs Liska writes:
> Indeed it does.
> But now that I know how to mark up a whole music expression with a
> custom music-property I see that it may not actually be what I need.
> Is it possible to read out the properties of music expressions in an
> engraver?
No.
> Or do these only respond to
Hi Harm,
Am 10.06.2018 um 15:15 schrieb Thomas Morley:
2018-06-09 23:59 GMT+02:00 Urs Liska :
You mean I should use set-object-property! rather than set!
(ly:music-property ?
Well, look at the example below (for custom-grob-properties):
{
\override NoteHead #'wtf = ##t
c'
d'
2018-06-09 23:59 GMT+02:00 Urs Liska :
> You mean I should use set-object-property! rather than set!
> (ly:music-property ?
Well, look at the example below (for custom-grob-properties):
{
\override NoteHead #'wtf = ##t
c'
d'
\once \override NoteHead #'color =
#(lambda (grob)
Am 09.06.2018 um 14:21 schrieb Thomas Morley:
2018-06-08 21:26 GMT+02:00 Urs Liska :
Hi,
is there anything wrong with adding an arbitrary property to a
SequentialMusic like that:
\version "2.19.80"
someNote = { c' d' }
#(set! (ly:music-property someNote 'foo) "bar")
\displayMusic
2018-06-08 21:26 GMT+02:00 Urs Liska :
> Hi,
>
> is there anything wrong with adding an arbitrary property to a
> SequentialMusic like that:
>
> \version "2.19.80"
>
> someNote = { c' d' }
>
> #(set! (ly:music-property someNote 'foo) "bar")
>
> \displayMusic \someNote
>
> ?
>
> The following is a
Hi,
is there anything wrong with adding an arbitrary property to a
SequentialMusic like that:
\version "2.19.80"
someNote = { c' d' }
#(set! (ly:music-property someNote 'foo) "bar")
\displayMusic \someNote
?
The following is a MWE of a new extension I plan for scholarLY, and it
seems to
