[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by addres
From: |
lilypond |
Subject: |
Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden) |
Date: |
Sat, 30 Dec 2017 03:00:25 -0800 |
On 2017/12/28 16:55:53, dan_faithful.be wrote:
I don’t consider myself qualified to answer your questions about use
cases, but
_if_ it is appropriate to ignore round-up-to-longer-rest for church
rests, it
looks easy to achieve that by moving the following term out of
calc_closest_duration_log() into its caller
calc_measure_duration_log().
to_boolean (me->get_property ("round-up-to-longer-rest”)
That would leave calc_closest_duration_log() doing exactly what it is
told in
terms of rounding.
Good idea, even if we should decide that we should ignore
usable-duration-logs completely. Here comes the next patch set that does
this and improves the regression test.
https://codereview.appspot.com/333340043/
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden), (continued)
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden), lilypond, 2017/12/26
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden), lemzwerg, 2017/12/26
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden), veronicalynnfierro, 2017/12/27
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden), nine . fierce . ballads, 2017/12/27
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden), lilypond, 2017/12/28
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden), lilypond, 2017/12/28
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden), lilypond, 2017/12/28
- Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by address@hidden),
lilypond <=