[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 4170 in lilypond: Patch: tie-formatting: s/Ste
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 4170 in lilypond: Patch: tie-formatting: s/Stem::note_head_positions/Stem::head_positions/ |
Date: |
Mon, 03 Nov 2014 09:17:13 +0000 |
Updates:
Status: Fixed
Labels: -Type-Enhancement -Patch-push Type-Defect Fixed_2_19_16
Comment #7 on issue 4170 by address@hidden: Patch: tie-formatting:
s/Stem::note_head_positions/Stem::head_positions/
https://code.google.com/p/lilypond/issues/detail?id=4170
Pushed to staging as
commit f8d9bf0a07e959b15e1876d1da9039547a39dee0
Author: David Kastrup <address@hidden>
Date: Sun Oct 19 13:21:44 2014 +0200
Issue 4170: tie-formatting:
s/Stem::note_head_positions/Stem::head_positions/
Looking at the return value here rather strongly suggests that the wrong
function is being called.
Unfortunately, I have not been able to construct an example triggering the
code in question. One would probably need to run some large scores through
LilyPond with a breakpoint set on the respective code to find an example.
So this is a replacement of code I do not really comprehend that looks
quite wrong by something that might have been intended, without actual
testing.
Triple ugh. The whole of tie-formatting-problem.cc is one rather appalling
cesspit responsible for a lot of our tie problems.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Lilypond-auto] Issue 4170 in lilypond: Patch: tie-formatting: s/Stem::note_head_positions/Stem::head_positions/,
lilypond <=