lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Text spanner shorten-pair


From: Trevor Bača
Subject: Re: Text spanner shorten-pair
Date: Tue, 12 Feb 2019 16:09:06 -0600

On Fri, Jan 25, 2019 at 11:38 AM Carl Sorensen <address@hidden> wrote:

 

 

From: Andrew Bernard <address@hidden>
Date: Friday, January 25, 2019 at 6:21 AM
To: lilypond-user Mailinglist <address@hidden>
Subject: Re: Text spanner shorten-pair

 

Hi Aaron,

 

I know. This then implies the NR is in error. Do we report a bug? [For the reason that being thrown off the scent I spent hours looking all in the interfaces to no avail.]

 

I think this is absolutely a bug.  It should not say shorten-pair applies to TextSpanners when it does not. 

 

There are three possible solutions I can see:

 

  1. Fix the description of shorten-pair to indicate which spanners it applies to
  2. Create a new interface e.g. shortenable-spanner-interface that contains shorten-pair, and then give that interface to all the grobs that accept shorten-pair (see dynamic-line-spanner-interface for a similar single-property interface).

 

The padding works. Seems inconsistent to me. Why do we leave TextSpanners out of the group?

  1. Add the shorten-pair property to the spanner-interface (or maybe the text-spanner interface) and make sure it works with all of the objects having that interface.

 

My preference right now would probably be #2.

 

I have not made an exhaustive study of this, but my initial thought is that there are two kinds of spanners.

 

Spanner type A goes from one grob to another (e.g. TextSpanner, glissando).  These spanners can be shortened by adding padding, because they will need to move away from the grobs that they connect when the padding is increased.

 

Spanner type B goes from one column to another (e.g. hairpin, pedal bracket).  These spanners don’t have grobs at their ends, so padding will not be effective at shortening them.  Hence the need for another method, as met by the shorten-pair property.

 

One could add the shorten-pair property to the type A spanners, but it’s not necessary to do so to shorten them.

 

I don’t know what I prefer for the long-term solution.  It would take more study and consideration of the pros and cons of each method.


Hi Carl, hi Andrew,

Also agreed that this is very much a bug; I've watched beginners get hit by it many times.

Question: why are there two ways to move around the ends of spanners (padding vs. shortening)? I can't think of a reason that's motivated by music notation. Which maybe implies that there's a fourth solution:

4. Collapse shorten-pair into padding (or vice versa), and preserve one (and only one) such property for *ALL* spanners.


Trevor.
 

--

reply via email to

[Prev in Thread] Current Thread [Next in Thread]