bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Broken hairpin placed too high on new line ("collision" with clef/key si


From: Reinhold Kainhofer
Subject: Broken hairpin placed too high on new line ("collision" with clef/key signature)
Date: Thu, 24 Jul 2008 20:52:19 +0200
User-agent: KMail/1.9.9

-----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: address@hidden, 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-----

Attachment: broken_hairpin_newline.ly
Description: Text Data

Attachment: broken_hairpin_newline.pdf
Description: Adobe PDF document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]