Re: KeyCancellation does not respond to break-visibility

2007-01-11 Thread Mats Bengtsson
Did you read the section on Key Signatures in the ordinary manual? /Mats Daniel Johnson wrote: When a key change occurs at a line break, in many (most?) editions the key is cancelled at the end of the first line, and not at the beginning of the subsequent line. According to the Fine Manual,

Re: KeyCancellation does not respond to break-visibility

2007-01-11 Thread Mats Bengtsson
Sorry! Forgot about what I wrote. What you show in your example looks like a plain bug, which seems to have existed at least since version 2.8. /Mats Mats Bengtsson wrote: Did you read the section on Key Signatures in the ordinary manual? /Mats Daniel Johnson wrote: When a key change occu

Re: KeyCancellation does not respond to break-visibility

2007-01-11 Thread Han-Wen Nienhuys
Mats Bengtsson escreveu: > Sorry! Forgot about what I wrote. What you show in your example looks > like a plain bug, which seems to have existed at least since version 2.8. have a look at explicitKeySignatureVisibility ; unfortunately, visibility is shared with KeySignature, but you can use printK

Issue 233 in project lilypond

2007-01-11 Thread codesite-noreply
Issue 233: secondary beam on wrong side http://code.google.com/p/lilypond/issues/detail?id=233 New issue report by hanwenn: \version "2.10.10" { << \new Staff {} \new Staff { g'16[ a'] } >> } Attachments: bug.preview.png 2K Issue attributes: Status: Fixed

Issue 233 in project lilypond

2007-01-11 Thread codesite-noreply
Issue 233: secondary beam on wrong side http://code.google.com/p/lilypond/issues/detail?id=233 Comment #1 by hanwenn: This was caused by Beam::get_beam_segments not doing me->get_property("beaming"). In most cases, this no problem, since the callback will already have been triggered due to anothe

Issue 233 in project lilypond

2007-01-11 Thread codesite-noreply
Issue 233: secondary beam on wrong side http://code.google.com/p/lilypond/issues/detail?id=233 Comment #2 by hanwenn: this was fixed in 2.11 by commit b772ceedf54b1dbb60af8d72f8386a5f12d10bbe Author: Joe Neeman <[EMAIL PROTECTED](none)> Date: Sun Nov 26 18:45:59 2006 +0200 fix Skyline::dis

Re: KeyCancellation does not respond to break-visibility

2007-01-11 Thread Mats Bengtsson
I don't see any combination of settings for these properties that can be used to obtain - both key cancellation and new key signature at the end of the line - only the new key signature at the beginning of the new line. As far as I can understand, the default setting corresponding to \override K

Re: KeyCancellation does not respond to break-visibility

2007-01-11 Thread Han-Wen Nienhuys
Mats Bengtsson escreveu: > I don't see any combination of settings for these properties that can be > used to > obtain > - both key cancellation and new key signature at the end of the line > - only the new key signature at the beginning of the new line. > > As far as I can understand, the default

Issue 215 in project lilypond

2007-01-11 Thread codesite-noreply
Issue 215: #(layout-set-staff-size X) doesn't use pt as the scale http://code.google.com/p/lilypond/issues/detail?id=215 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_11 -- You received this message be

Issue 87 in project lilypond

2007-01-11 Thread codesite-noreply
Issue 87: midi grace loses sync http://code.google.com/p/lilypond/issues/detail?id=87 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_11 fixed_2_10_11 -- You received this message because you are listed

Issue 85 in project lilypond

2007-01-11 Thread codesite-noreply
Issue 85: midi non-standard tuplet loses synchronisation http://code.google.com/p/lilypond/issues/detail?id=85 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_11_11 fixed_2_10_11 -- You received this messag

Issue 231 in project lilypond

2007-01-11 Thread codesite-noreply
Issue 231: convert-ly and New_dynamic_performer http://code.google.com/p/lilypond/issues/detail?id=231 Comment #1 by hanwenn: (No comment was entered for this change.) Issue attribute updates: Status: Fixed Labels: fixed_2_10_11 fixed_2_11_11 -- You received this message becaus