Re: Tweaking glissando timing stems

[Leo Correia de Verdier]

Dear Harm and list!

The chords were not that hard to implement. What I did was:

1) Removing the overrides for NoteHead.transparency and NoteHead.Y-offset from 
glissandoStemsOn and glissandoStemsOff. Transparency is set for individual 
noteheads and used to determine wether a notehead should be printed as usual or 
”glissed through”.

2) Adding transparency to the conditions for moving a notehead to the glissando 
line.
        (ly:grob-property (car nhd-staff-pos) 'transparent #f)

3) resetting the noteheads Y-position only after testing that the notehead in 
question should be moved at all, as in the earlier code you’d written (it vas 
still in the document, just commented out and replaced by just the variable val)
        (+ (/ (cdr nhd-staff-pos) -2) val)

This has not been seriously stresstested, though. It’s still on a "seems to 
work” level. A more beautiful solution would probably be to use a dedicated 
property instead of piggybacking it on transparency and assuming them identical.

Another thing I found is that TextScript placements are reset as in the example 
provided. Can you see any solution for this?

Thanks a lot!
/Leo

glissando-stems-engraver-text-script-example.ly
Description: Binary data

> 26 okt. 2021 kl. 01:05 skrev Thomas Morley <thomasmorley65@gmail.com>:
> 
> Am Mo., 25. Okt. 2021 um 12:00 Uhr schrieb Leo Correia de Verdier
> <leo.correia.de.verdier@gmail.com>:
>> 
>> Don’t worry, you’re doing far more on this than anyone could reasonably 
>> expect.
>> 
>> The final result should be something along these lines, but what I was 
>> asking about is just the chord possibility. I have looked a little more into 
>> the code and it’s far far above my level, but I’ve found som places I could 
>> possibly act on…
>> If you don’t have time for it I would be grateful for hints about what I 
>> could mess around with where in the code.
>> 
>> 
>> Thanks!
>> /Leo
> 
> Hi Leo,
> 
> thanks for the image, I think I understood.
> Though, I will first improve the current coding to make it working
> with all usual basic cases (and cure some bugs), before I try to
> implement other features. Got already some great hints from Jean and
> Aaron.
> Maybe next weekend ...
> 
> Cheers,
>  Harm