Am Sa., 16. Feb. 2019 um 09:00 Uhr schrieb Andrew Bernard
:
>
> Hi Harm,
>
> This is great. It locates unterminated glissandi, but in my case it was just
> stupidity - they were at the end of the score with no note following. This
> amazing code of yours does not, in my setting at least, locate o
Hi Harm,
This is great. It locates unterminated glissandi, but in my case it was
just stupidity - they were at the end of the score with no note following.
This amazing code of yours does not, in my setting at least, locate or
catch the 'programming error: overwriting glissando' issue.
Thanks so
with any code I tried.
Do you apply some Glissando-overrides?
Maybe some coding is not as clean as wished.
Anyway, it's pretty easy to get the "unterminated glissando"-warning.
To check in a long, complicated file I wrote a helper-tool.
It checks for grob::is-live?, sufficient for all
should I look
for?
Andrew
On Fri, 15 Feb 2019 at 23:01, Andrew Bernard
wrote:
> I get this:
>
> programming error: overwriting glissando
> continuing, cross fingers
> warning: unterminated glissando
> warning: unterminated glissando
> Preprocess
I get this:
programming error: overwriting glissando
continuing, cross fingers
warning: unterminated glissando
warning: unterminated glissando
Preprocessing graphical objects..
What does this mean actually? How can a glissando be unterminated - surely
it connects to the next available note. I
