2016-01-12 23:05 GMT+01:00 Pierre Perol-Schneider
<pierre.schneider.pa...@gmail.com>:
> Hi Harm,
>
> 2016-01-12 21:24 GMT+01:00 Thomas Morley <thomasmorle...@gmail.com>:
>
>>
>> I've always found it a little so-so, to define custom markup-commands
>> only combining a personal choice of preexisting markup-commands.
>
>
> I fully agree, it's just that my scheme knowledge is also a little so-so ;)
> Actually I tried to. Without success.
> Basically the idea was to make the 'whiteout' command to accept a color
> override. E.g. :
>
> \version "2.19.35"
>
> \markup {
> \combine
> \filled-box #'(-1 . 18) #'(-3 . 4) #1
> \override #'(style . outline)
> \override #'(thickness . 3)
>
> %% here :
> \override #'(color . red)
You can't hope a markup-command will accept an override for a
property, if said property isn't declared in any way.
Thus, I tried to write a markup-command aiming exactly this use-case.
Though, there might be a bug in `stencil-whiteout-outline', Paul cc-ed.
Look at:
\markup \stencil
#(stencil-whiteout-outline
(make-filled-box-stencil '(-1 . 1) '(-1 . 1))
0.5
red
16
1)
\markup \stencil
#(stencil-whiteout-outline
(stencil-with-color (make-filled-box-stencil '(-1 . 1) '(-1 . 1)) green)
0.5
red
16
1)
First one is ok.
But in the second one the color from the stencil is taken (green) and
the specified (red) is ignored.
Will investigate more detailed the upcoming days.
Cheers,
Harm
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
