Menu

#448 KeyCancellation and KeySignatures in unnecessarily separated columns

Accepted
nobody
None
Ugly
2015-09-16
2007-09-05
Anonymous
No

Originally created by: *anonymous

Originally created by: gpermus@gmail.com

Big unwanted space in second bar:

:::TeX
\version "2.11.31"
\paper { ragged-right = ##t }
\score {
    \new GrandStaff <<
    \new Staff { c'1 \key es \major }
    \new Staff { \key des \major s1 \key c \major }
    >>
}
1 Attachments

Related

Issues: #4157
Issues: #4263

Discussion

  • Google Importer

    Google Importer - 2007-09-05

    Originally posted by: mats.ben...@s3.kth.se

    A workaround in this particular case is to add
    \override Staff.KeyCancellation #'X-extent = #'(0 . 0)
    in the lower stave.

    One question is what the desired layout is in the following situation:

    :::TeX
    \version "2.11.31"
    \paper { ragged-right = ##t }
    \score {
        \new GrandStaff <<
        \new Staff { c'1 \key es \major }
        \new Staff { \key des \major s1 \key d \major }
        >>
    }
    

    Should the key signature in the upper stave be aligned with the key cancellation or the new key signature in the lower stave or should it be centered over both? Finding a solution that handles both these examples well seems difficult.

     

    Last edit: Simon Albrecht 2015-09-16
  • Google Importer

    Google Importer - 2008-06-09

    Originally posted by: hanw...@gmail.com

    (No comment was entered for this change.)

    Labels: -Priority-Medium Priority-Low

     
  • Google Importer

    Google Importer - 2011-09-16

    Originally posted by: pkx1...@gmail.com

    Still an issue in 2.15.11

    Summary: KeyCancellation on a staff in a staff group causes ugly spacing problem
    Owner: ---
    Labels: -Type-Defect -Priority-Low Type-Ugly

     
  • Google Importer

    Google Importer - 2011-09-30

    Originally posted by: k-ohara5...@oco.net

    For examples I went to Mahler, who loved key changes.  I found that the new key signature is run up against the cancellation, even in Edition Peters.  I find that harder to read than what LilyPond does.

    I suggest we want the KeySignatures and KeyCancellations each left-aligned in their own columns, but allow those columns to mesh when there is room.  This would put the es\major signature over the cancellation in the bug example, but still align nicely for the situation Mats mentions above.

    One implementation would be to have horizontal skylines calculated for KeyCancellation and KeySignature for use in break-alignment-interface::calc-positioning-done, and change the space-alist specification beteween KeyCancellation and KeySignature.

     
  • Simon Albrecht

    Simon Albrecht - 2015-09-16
    • summary: KeyCancellation and KeySignatures in un-necessarily separated columns --> KeyCancellation and KeySignatures in unnecessarily separated columns
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -2,14 +2,17 @@
    
     *Originally created by:* [gpermus@gmail.com](http://code.google.com/u/gpermus@gmail.com/)
    
    -%\{&nbsp; Big unwanted space in second bar&nbsp; %\}
    +Big unwanted space in second bar:
    
    +~~~~
    +:::TeX
     \version "2.11.31"
    -\paper \{ ragged-right = \#\#t \}
    -\score \{
    -&nbsp;&nbsp;&nbsp; \new GrandStaff
    -&nbsp;&nbsp;&nbsp; &lt;&lt;
    -&nbsp;&nbsp;&nbsp; \new Staff \{ c'1 \key es \major \}
    -&nbsp;&nbsp;&nbsp; \new Staff \{ \key des \major s1 \key c \major \}
    -&nbsp;&nbsp;&nbsp; &gt;&gt;
    -\}
    +\paper { ragged-right = ##t }
    +\score {
    +    \new GrandStaff
    +    <<
    +    \new Staff { c'1 \key es \major }
    +    \new Staff { \key des \major s1 \key c \major }
    +    >>
    +}
    +~~~~
    
    • Needs: -->
    • Patch: -->
     
  • Simon Albrecht

    Simon Albrecht - 2015-09-16