[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 471 in lilypond: explicitKeySignatureVisibility shouldn't be neces
From: |
codesite-noreply |
Subject: |
Issue 471 in lilypond: explicitKeySignatureVisibility shouldn't be necessary here |
Date: |
Fri, 14 Sep 2007 11:33:57 -0700 |
Issue 471: explicitKeySignatureVisibility shouldn't be necessary here
http://code.google.com/p/lilypond/issues/detail?id=471
New issue report by gpermus:
%{
The setting of Staff.explicitKeySignatureVisibility shouldn't be
necessary in the following example:
%}
\version "2.11.32"
\score {
\new StaffGroup \relative c''{
\new Staff
\key f \major
c1 c^"Unwanted extra space" \break
<< { c1 c }
\new Staff {
\key f \major
c1 c
}
>>
c1 c^"Fixed here" \break
<< { c1 c }
\new Staff {
\once \set Staff.explicitKeySignatureVisibility =
#end-of-line-invisible
\key f \major
c1 c
}
>>
}
}
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Enhancement Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Issue 471 in lilypond: explicitKeySignatureVisibility shouldn't be necessary here,
codesite-noreply <=