From c5dcd1764a635088bea85e46e0f5be3d3b134a3f Mon Sep 17 00:00:00 2001 From: Han-Wen Nienhuys Date: Tue, 23 Jul 2002 22:33:30 +0000 Subject: [PATCH] print demerits --- Documentation/user/preface.itely | 20 ++++++++++++++++++-- lily/gourlay-breaking.cc | 5 +++++ lily/staff-spacing.cc | 7 ++++--- 3 files changed, 27 insertions(+), 5 deletions(-) diff --git a/Documentation/user/preface.itely b/Documentation/user/preface.itely index 8d947eb6ca..9cd0714f97 100644 --- a/Documentation/user/preface.itely +++ b/Documentation/user/preface.itely @@ -13,8 +13,24 @@ happened, Han-Wen accidentally wanted to print out some parts from a score, so he started looking at the software, and he quickly got hooked. It was soon decided that MPP was a dead end. After lots of philosophizing and heated e-mail exchanges Han-Wen started LilyPond in -1996. This time, Jan got sucked into Han-Wen's new project. The rest -is, as they say, history. +1996. This time, Jan got sucked into Han-Wen's new project. + +A stable release, like version 1.6 is a good moment to contemplate the +past and the present. Looking back we notice something curious: when +we started, we mistook our naivite for self confidence, and our +interested was piqued by music typography. LilyPond was our pet +project. Somewhere along the line, it grew out of our hands. Today, we +can't tell whether we are doing LilyPond, or LilyPond is doing +us. Working on it has become more than a simple hobby. We're not sure +how this happened, but we think + + overestimated our slef the combination of high energy strong + + + + one thing that +stands out. Somewhere + [TODO some more here.] diff --git a/lily/gourlay-breaking.cc b/lily/gourlay-breaking.cc index ac250e9684..d01dd461c0 100644 --- a/lily/gourlay-breaking.cc +++ b/lily/gourlay-breaking.cc @@ -6,6 +6,7 @@ (c) 1997--2002 Han-Wen Nienhuys */ #include // rint +#include #include "gourlay-breaking.hh" #include "column-x-positions.hh" @@ -167,6 +168,10 @@ Gourlay_breaking::do_solve () const i = prev; } + if (verbose_global_b) + printf("Optimal demerits: %f\n", optimal_paths.top().demerits_f_); + + if (optimal_paths.top ().demerits_f_ >= infinity_f) warning (_ ("No feasible line breaking found")); diff --git a/lily/staff-spacing.cc b/lily/staff-spacing.cc index 81bc06000d..9e995156cf 100644 --- a/lily/staff-spacing.cc +++ b/lily/staff-spacing.cc @@ -168,8 +168,6 @@ Staff_spacing::extremal_break_aligned_grob (Grob *separation_item, Direction d, return last_grob; } -/* -*/ void Staff_spacing::get_spacing_params (Grob *me, Real * space, Real * fixed) { @@ -200,7 +198,10 @@ Staff_spacing::get_spacing_params (Grob *me, Real * space, Real * fixed) &last_ext); if (!last_grob) { - programming_error ("empty break column? --fixme"); + /* + we used to have a warning here, but itgenerates a lot of + spurious error messages. + */ return ; } -- 2.39.5