#2313 BarNumber and SystemStartBracket collisions are not handled

[Anonymous]

Originally created by: *anonymous

Originally created by: colingh...@gmail.com

Reinhold reports a bug in this posting:

http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/33435

His original post follows. His code calls for version 2.15.30 but in fact the bug is present in earlier versions. I have confirmed it on 2.15.29.

If the first staff of a score a group bracket uses a bass clef, the bar
number (when center-aligned) collides with the bracket. Attached is an
example.

Cheers,
Reinhold

\version "2.15.30"

\score {
  \new StaffGroup <<
    \new Staff \relative c {
      \override Score.BarNumber #'self-alignment-X = #CENTER % center-aligned
%       \bar""
      \clef "bass"
      c1 | c1 | c | c | \break
      c1 | c1 | c | c | \break
      c1 | c1 | c | c | \break
      c1 | c1 | c | c | \break
    }
    \new Staff \relative c {
%       \bar""
      \clef "bass"
      c1 | c1 | c | c | \break
      c1 | c1 | c | c | \break
      c1 | c1 | c | c | \break
      c1 | c1 | c | c | \break
    }

  >>
}

[Google Importer]

Originally posted by: simon.al...@mail.de

I just tested this with 2.19.8. Basically, the reported behaviour persists, but:
– It does not have anything to do with the bass clef.
– The default behaviour is OK, the problem appears only if alignment is overridden.
– It’s very easily worked around by using Y-offset = 4 on BarNumber.

The summary should thus read “BarNumber and SystemStartBracket collisions are not handled”.

I consider this problem very small, even negligible. Of course, one might teach Lily to avoid collisions between SystemStartBracket and BarNumber, but to me it seems a little unnecessary. The default placement of BarNumber is good-looking and correct.

[Google Importer]

Originally posted by: tdanielsmusic

#1 is essentially correct.  The positioning of the default bar number is indeed "good-looking and correct".  The collision with the SystemStartBracket occurs only when \override BarNumber.self-alignment-X = 0 is specified, but now the collision occurs with both bass and treble clefs, as Simon says.  I think the dependence on clefs changed when the sky-lining code was improved to use the actual outline of grobs rather than bounding boxes sometime during the 2.17 development phase.  So the bug is now actually rather more prevalent than before, although I agree it is hardly severe.

I'm changing the summary as suggested by Simon.

Trevor

Summary: BarNumber and SystemStartBracket collisions are not handled

[Google Importer]

Originally posted by: simon.al...@mail.de

(No comment was entered for this change.)

Labels: -OpSys-All