Issue 4390042: lily/stem-engraver.cc: Improve error message for incompatible durations while stemming

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment
d :	mark current comment as done

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :	save comment
<Esc> :	cancel edit

Issue 4390042: lily/stem-engraver.cc: Improve error message for incompatible durations while stemming (Closed)

Can't Edit
Can't Publish+Mail
Start Review

Created:
13 years ago by dak

Modified:
13 years ago

Reviewers:

CC:
lilypond-devel_gnu.org

Visibility:
Public.

Description

lily/stem-engraver.cc: Improve error message for incompatible durations while stemming The error messages for incompatible durations go down the drain when the stem duration log is negative. This changes the warnings to fractions. Possibly it would be smarter to use Lilypond lengths, but there does not seem to be an easily accessible printer from C++.

Patch Set 1 #

Created: 13 years ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+28 lines, -4 lines)			Patch
	A	input/regression/incompatible-stem-warning.ly	View		1 chunk	+22 lines, -0 lines	0 comments	Download
	M	lily/stem-engraver.cc	View		1 chunk	+6 lines, -4 lines	0 comments	Download

Messages

Total messages: 1

Expand All Messages | Collapse All Messages

dak

13 years ago (2011-04-13 10:33:58 UTC) #1

Pushed since there does not seem much point in jumping through more hoops
because nobody can be interested in the bug report.

Expand All Messages | Collapse All Messages