Colin Hall writes:
> Colin Hall writes:
>
>> Karol Majewski writes:
>>
>>> Hi,
>>>
>>> Issue 3203 isn't fully solved. There is no SpanBar when including centered
>>> dynamics:
>>>
>>> \version "2.17.14"
>>> \new PianoStaff<<
>>> \new Staff { c''1 c''1 }
>>> \new Dynamics { s1 s1 \f }
>>> \n
Colin Hall writes:
> Karol Majewski writes:
>
>> Hi,
>>
>> Issue 3203 isn't fully solved. There is no SpanBar when including centered
>> dynamics:
>>
>> \version "2.17.14"
>> \new PianoStaff<<
>> \new Staff { c''1 c''1 }
>> \new Dynamics { s1 s1 \f }
>> \new Staff { c''1 c''1 }
>>
>> K
Karol Majewski writes:
> Hi,
>
> Issue 3203 isn't fully solved. There is no SpanBar when including centered
> dynamics:
>
> \version "2.17.14"
> \new PianoStaff<<
> \new Staff { c''1 c''1 }
> \new Dynamics { s1 s1 \f }
> \new Staff { c''1 c''1 }
>>>
>
> Karol
The fix for this recent proble
Karol Majewski writes:
> Hi,
>
> Issue 3203 isn't fully solved. There is no SpanBar when including centered
> dynamics:
>
> \version "2.17.14"
> \new PianoStaff<<
> \new Staff { c''1 c''1 }
> \new Dynamics { s1 s1 \f }
> \new Staff { c''1 c''1 }
>>>
And yes, it is the "cleanup" commit from
Hi,
Issue 3203 isn't fully solved. There is no SpanBar when including centered
dynamics:
\version "2.17.14"
\new PianoStaff<<
\new Staff { c''1 c''1 }
\new Dynamics { s1 s1 \f }
\new Staff { c''1 c''1 }
>>
Karol
___
bug-lilypond mailing list
bug-
Hello,
2013/3/13 m...@mikesolomon.org
> \relative c' {
> \override TupletNumber.font-size = #10
> \times 2/3 { d d d }
> }
>
> Ideally, the tuplet number should avoid the collision by shifting up. The
> bracket should shift up as well.
> This is currently difficult, as the TupletNumber is a
Hello,
2013/3/10 Clément
> Using oneVoice position (or indirectly, partcombineApart) while making a
> beam go
> over a rest destroys vertical alignment in a staff.
>
> Thank you for the report. This has been added as
http://code.google.com/p/lilypond/issues/detail?id=3242
Marek
bug squad member
\relative c' {
\override TupletNumber.font-size = #10
\times 2/3 { d d d }
}
Ideally, the tuplet number should avoid the collision by shifting up. The
bracket should shift up as well.
This is currently difficult, as the TupletNumber is a child of the tuplet
bracket and therefore dependent o
