[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: how do Slur #'positions work?
From: |
Mats Bengtsson |
Subject: |
Re: how do Slur #'positions work? |
Date: |
Tue, 05 Jun 2007 23:06:45 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20061113 Debian/1.7.8-1sarge8 |
I couldn't decipher all details in the implementation, but it seems
that LilyPond first generates a list of possible positions for the
left and right end of the slur. Normally, it goes through the list
and finds the slur that "looks the best", i.e. gets the highest
score according to some criterion. When you instead specify
the positions property, LilyPond will still go through its list
of alternatives and choose the one that's closest to what you
specified. In this case, it seems that you wanted something
that was higher up than what's available in the list, so that's
why you get the same result in both cases.
/Mats
Graham Percival wrote:
Tracking down a potential bug; in this example, both slurs have the
same height. Shouldn't the second slur be much higher? Could the
vertical spacing code be moving the second slur down?
Cheers,
- Graham
\version "2.11.24"
\relative c'' {
\slurUp
\override Slur #'positions = #'(5 . 5)
c8.( b16) c8. b16
\override Slur #'positions = #'(30 . 30)
c8.( b16) c8. b16
}
_______________________________________________
lilypond-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=============================================
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: address@hidden
WWW: http://www.s3.kth.se/~mabe
=============================================