change staff produces long stems

2011-04-22 Thread Graham Percival
http://code.google.com/p/lilypond/issues/detail?id=1612 My reading of the situation is this: 1. we should turn off beam collisions for cross-staff stems 2. we should document that such beam collisions are turned off, as: - a @knownissue in the cross-staff stem node - in the changes.tely 3.

Turns off beam collision for cross-staff beams (issue4423062)

2011-04-22 Thread mtsolo
Reviewers: , Description: Turns off beam collision for cross-staff beams Please review this at http://codereview.appspot.com/4423062/ Affected files: M lily/beam-collision-engraver.cc Index: lily/beam-collision-engraver.cc diff --git a/lily/beam-collision-engraver.cc

Update about beam collision in the docs. (issue4431058)

2011-04-22 Thread mtsolo
Reviewers: , Message: I did my best to figure out a way to handle automatic beams before staff changes, but the best I could come up with was a system where a beam was created every time the automatic beam engraver considered starting a beam, which leads to a lot of dead grobs that could

Re: Turns off beam collision for cross-staff beams (issue4423062)

2011-04-22 Thread percival . music . ca
LGTM http://codereview.appspot.com/4423062/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Update about beam collision in the docs. (issue4431058)

2011-04-22 Thread percival . music . ca
LGTM http://codereview.appspot.com/4431058/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Beamed stems too long when avoiding low note in other voice

2011-04-22 Thread Graham Percival
Now that Mike's fixed 1612, let's look at the other remaining beaming problem. http://code.google.com/p/lilypond/issues/detail?id=1613 This issue is still open and produces bad output with git master. Anybody have any ideas? Cheers, - Graham ___

Re: Beamed stems too long when avoiding low note in other voice

2011-04-22 Thread Han-Wen Nienhuys
I'll have a look. On Fri, Apr 22, 2011 at 10:55 AM, Graham Percival gra...@percival-music.ca wrote: Now that Mike's fixed 1612, let's look at the other remaining beaming problem. http://code.google.com/p/lilypond/issues/detail?id=1613 This issue is still open and produces bad output with git

Re: Event listener to extract (some) music events. (issue4373046)

2011-04-22 Thread n . puttock
http://codereview.appspot.com/4373046/diff/12002/ly/event-listener.ly File ly/event-listener.ly (right): http://codereview.appspot.com/4373046/diff/12002/ly/event-listener.ly#newcode102 ly/event-listener.ly:102: #(define (print-line engraver values) If you make `values' a `rest' argument you

Re: Event listener to extract (some) music events. (issue4373046)

2011-04-22 Thread Neil Puttock
On 18 April 2011 15:30, percival.music...@gmail.com wrote: On 2011/04/18 14:09:52, hanwenn wrote: In that case, it would probably be cleaner to hook into the event listener framework directly, without having an engraver in between.  The Scheme engraver mechanism is really for creating

Compressabilty

2011-04-22 Thread Olivier Chamley
Hi everybody... I have some difficulties to understand the minimum-distance setting, I just hopped that somebody could explain it to me. According to current documentation, minimum-distance is the smallest allowable vertical distance, and basic-distance the default one. So with the following

Re: Compressabilty

2011-04-22 Thread Carl Sorensen
On 4/22/11 1:32 PM, Olivier Chamley olivier.cham...@free.fr wrote: Hi everybody... I have some difficulties to understand the minimum-distance setting, I just hopped that somebody could explain it to me. According to current documentation, minimum-distance is the smallest allowable

Ignore accidentals of the beam itself when guessing an initial configuration. (issue4450052)

2011-04-22 Thread mtsolo
http://codereview.appspot.com/4450052/diff/1/lily/beam.cc File lily/beam.cc (right): http://codereview.appspot.com/4450052/diff/1/lily/beam.cc#newcode1221 lily/beam.cc:1221: This solution doesn't work for: \new Staff { { \voiceOne s16 fis'' } \\ { \voiceTwo e4 e } \\ {

Re: Ignore accidentals of the beam itself when guessing an initial configuration. (issue4450052)

2011-04-22 Thread Han-Wen Nienhuys
On Fri, Apr 22, 2011 at 6:20 PM, mts...@gmail.com wrote: \new Staff {     { \voiceOne s16 fis'' }   \\   { \voiceTwo e4 e }   \\   { \voiceFour   f''8 e'' gis'' gis'' } } One interesting thing is that it is the stems, not the noteheads, that are pushing this down.  If you remove