Re: 2.19.80 restNumberThreshold

[Paul Scott]

On Sat, Nov 04, 2017 at 04:22:42PM +0100, David Kastrup wrote:
> David Kastrup <address@hidden> writes:
> 
> > Paul Scott <address@hidden> writes:
> >
> >> For some time restNumberThreshold has not worked for me.
> >>
> >> \version "2.19.80"
> >>
> >> \relative{
> >>   c''1
> >>   \set Score.restNumberThreshold = #0 R
> >>   \set Score.restNumberThreshold = #1 R
> >> }
> >>
> >> This does not put a "1" over the 2nd bar.  What have I missed?
> >
> > Huh.  Take a look at
> >
> > \version "2.19.80"
> >
> > \relative{
> >   c''1
> >   \set Score.restNumberThreshold = #0 R1*3 R1*3
> >   \set Score.restNumberThreshold = #1 R1*3 R1*3
> >   \set Score.restNumberThreshold = #2 R1*3 R1*3
> >   \set Score.restNumberThreshold = #3 R1*3 R1*3
> > }
> >
> > This looks more than weird.
> 
> Actually, using \compressFullBarRests it looks sort-of reasonable.

I did remember that later.  It's in my regular code.
It looks like \compressMMRests has replaced \compressFullBarRests even
though the latter still works.

Is that right?

Paul


> The
> only irritating thing is that setting the restNumberThreshold already
> affects a multimeasure rest _ending_ at the same moment.  So the
> engraver should likely remember the setting active at the start of the
> (partial?) rest.
> 
> -- 
> David Kastrup
>