2017-10-23 21:28 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> So how to proceed with 5220?
>> I'm confident I could adapt your change once it is in master
>
> More like "use it". I don't think you need to do anything with it.
>
>> and maybe even prepare the engravers so that a follow up
Thomas Morley writes:
> So how to proceed with 5220?
> I'm confident I could adapt your change once it is in master
More like "use it". I don't think you need to do anything with it.
> and maybe even prepare the engravers so that a follow up could
> implement the idea of https://codereview.app
2017-10-23 15:29 GMT+02:00 David Kastrup :
> David Kastrup writes:
>
>>> Is this appropiate?
>>
>> "cause" here is the actual tie event triggering the column. I think
>> that it should rather be the first tie, making the
>> LaissezVibrerTieColumn a grob with ultimately identifiable cause but not
David Kastrup writes:
>> Is this appropiate?
>
> "cause" here is the actual tie event triggering the column. I think
> that it should rather be the first tie, making the
> LaissezVibrerTieColumn a grob with ultimately identifiable cause but not
> a directly caused grob. Then it should be ignore
Thomas Morley writes:
> Hi all,
>
> here:
> https://sourceforge.net/p/testlilyissues/issues/5220/#f5aa/ed76
> I wrote that \parenthesize\laissezVibrer does not work because
> LilyPond tries to parenthesize LaissezVibrerTieColumn as well.
>
> And indeed, with the code below _two_ grobs are affecte
Hi all,
here:
https://sourceforge.net/p/testlilyissues/issues/5220/#f5aa/ed76
I wrote that \parenthesize\laissezVibrer does not work because
LilyPond tries to parenthesize LaissezVibrerTieColumn as well.
And indeed, with the code below _two_ grobs are affected:
LaissezVibrerTieColumn and LaissezV
