Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2675)

Issue 572550043: Avoid failed assertion in stem tremolo code (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
5 years ago by dak
Modified:
4 years, 2 months ago
Reviewers:
Keith
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

Avoid failed assertion in stem tremolo code Example code triggering the problem: \relative { a32 8..:32 }

Patch Set 1 #

Total comments: 6

Patch Set 2 : Incorporate Keith's feedback #

Unified diffs Side-by-side diffs Delta from patch set Stats (+7 lines, -1 line) Patch
M lily/stem-tremolo.cc View 1 1 chunk +7 lines, -1 line 0 comments Download

Messages

Total messages: 4
Keith
If I understand, the example \relative { a32 8..:32 } fails the assertion in the ...
5 years ago (2019-04-03 08:16:22 UTC) #1
Keith
https://codereview.appspot.com/572550043/diff/560590043/lily/stem-tremolo.cc File lily/stem-tremolo.cc (left): https://codereview.appspot.com/572550043/diff/560590043/lily/stem-tremolo.cc#oldcode175 lily/stem-tremolo.cc:175: Interval ph = stem->pure_y_extent (stem, 0, INT_MAX); My suggested ...
5 years ago (2019-04-03 17:10:50 UTC) #2
dak
Incorporate Keith's feedback
5 years ago (2019-04-08 16:14:53 UTC) #3
dak
5 years ago (2019-04-08 16:17:16 UTC) #4
Thanks for looking at this, Keith!  I've tried to make a version that does the
right thing with regard to the assertion failure.  That does not address the
root cause of the problem, nor does it fix the centering thing you pointed out. 
Quite lacklustre.

https://codereview.appspot.com/572550043/diff/560590043/lily/stem-tremolo.cc
File lily/stem-tremolo.cc (left):

https://codereview.appspot.com/572550043/diff/560590043/lily/stem-tremolo.cc#...
lily/stem-tremolo.cc:182: ph = ph - ph.center ();
On 2019/04/03 08:16:22, Keith wrote:
> There is the obvious problem that line 182 destroys the effort of line 181.  
It
> reports every stem-tremolo to be centered on the central staff-line, which
makes
> line-spacing less accurate but could easily go un-noticed.

This is likely the famous "somebody must have been something" phenomenon.  Since
this does not concern the segfaulting, I am leaving this for someone else to
fix.  Ok, I'll add a TODO.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b