[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 370 in project lilypond
From: |
codesite-noreply |
Subject: |
Issue 370 in project lilypond |
Date: |
Tue, 05 Jun 2007 21:54:04 -0700 |
Issue 370: slur #'positions silently does not place slur at actual position
http://code.google.com/p/lilypond/issues/detail?id=370
New issue report by gpermus:
%{ Mats commented:
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.
%}
\version "2.11.24"
\paper{ragged-right=##t}
\relative c'' {
\slurUp
\override Slur #'positions = #'(5 . 5)
c8.( b16) c8. b16
\override Slur #'positions = #'(30 . 30)
c8.( b16) c8. b16
}
Attachments:
foo.preview.png 2.8 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 370 in project lilypond,
codesite-noreply <=