[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 427 in lilypond: ugly collision slur and phrasing slur
From: |
codesite-noreply |
Subject: |
Issue 427 in lilypond: ugly collision slur and phrasing slur |
Date: |
Fri, 27 Jun 2008 13:42:24 -0700 |
Issue 427: ugly collision slur and phrasing slur
http://code.google.com/p/lilypond/issues/detail?id=427
Comment #5 by ahawryluk:
The difference almost certainly lies in slur-engraver.cc and
phrasing-slur-engraver.cc, since they have identical "include"
sections. I'm guessing
that the culprit is the stop_translation_timestep() method, since the
Slur_engraver
version has a bunch of add_extra_encompass commands that are not found
in the
Phrasing_slur_engraver.
There are a few other differences that appear unintentional, like more
robust error
checking in the Slur version, and no acknowledge_tuplet_number in
Phrasing_slur_engraver.
Here's a better example of the difference
\version "2.11.49"
\paper { ragged-right=##t }
{
\key e \major
b'1(\( \break
e')\)
}
--
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 427 in lilypond: ugly collision slur and phrasing slur,
codesite-noreply <=