-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When a hairpin is broken due to a line break, the second part of the hairpin -- although it start a little bit after the clef/key signature -- is placed too high as if it would collide with the clef or key signature. If the clef does not go out of the staff lines boundary (i.e. bass clef), the second part is placed correctly. I guess it must be just a single pixel or so that causes the bounding boxes of the clef/key signature and the hairpin to collide and moves the hairpin up
Attached is a simple test case to reproduce. Can this be added to the bug tracker so that it doesn't get lost? Note that other spanners (like line spanners) do not exhibit this problem. Cheers, Reinhold - -- - ------------------------------------------------------------------ Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIiM9lTqjEwhXvPN0RAozRAKCn57JsBGkQ6Mx7oq6EGydSJur2UQCdHruL NNEgciIZXB/ChvL809o0DRc= =8zbq -----END PGP SIGNATURE-----
\version "2.11.46"
#(ly:set-option 'debug-skylines #t)
% In this example, the hairpin (broken by a line break) is placed too high in
% the second and third staff, because apparently the clef and the key signature
% get in its way...
\relative b' {
\dynamicUp \time 2/4
\key a \major
b\< b\! | b\< b | \break
% Key signature makes the second part of the hairpin move up
b b\! | \key c \major b\< b | \break
% clef also causes the problem:
b b\! | \clef "bass" d,,\< d | \break
% bass clef works, because its extents do not go beyond the staff lines
d d\! |
}
broken_hairpin_newline.pdf
Description: Adobe PDF document
_______________________________________________ bug-lilypond mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-lilypond
