- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.



---

** [issues:#2199] Mark_engraver in StaffGroup misplaces marks at top of Score**

**Status:** Started
**Created:** Sat Jan 07, 2012 11:50 AM UTC by Anonymous
**Last Updated:** Tue Feb 27, 2018 08:03 AM UTC
**Owner:** Dan Eble


align outside-staff grobs vertically in staff groups

In any context in which a Vertical_align_engraver creates a
StaffGrouper, it also sees to it that all outside-staff grobs created
in the immediate context become y-axis children of the StaffGrouper.

Any such grobs which are later processed by the after-line-breaking
callback ly:side-position-interface::move_to_extremal_staff are moved
to the extremal staff of the group, not of the entire system.

http://codereview.appspot.com/331650043

****

*Originally created by:* *anonymous

*Originally created by:* 
[janek.li...@gmail.com](http://code.google.com/u/100525084317801742451/)

This has been reported 
[two](http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00395.html) 
[times](http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00111.html) 
in lilypond-user.

"Mark\_engraver" or "Metronome\_mark\_engraver" should be moveable to the
StaffGroup \(and alike: GrandStaff, ChoirStaff, etc.\) context \(and work\!\!\).

~~~~
:::TeX
%%%% Snippet

\version "2.13.24"

music = \repeat unfold 5 {
  \repeat unfold 5 c'1
  \mark \default
}

\score {
  <<
    \new Staff {
      s1*0^"Marks should NOT be above this Staff (i.e. above the Score)!"
      \music
    }
    \new StaffGroup {
      <<
        \new Staff {
          s1*0^"Marks should be above the StaffGroup"
          \music
        }
        \new Staff {
          \music
        }
      >>
    }
  >>
  \layout {
    \context {
      \Score
      \remove "Mark_engraver"
      % same for "Metronome_mark_engraver"
      \remove "Staff_collecting_engraver"
    }
    \context {
      \StaffGroup
      \consists "Mark_engraver"
      \consists "Staff_collecting_engraver"
      % same for "Metronome_mark_engraver"
    }
  }
}


%% Note that it works if we move it to the Staff level (instead of the
%% StaffGroup).  But engravers at the StaffGroup level is required for
%% example if the first staff of the StaffGroup is removed, using
%% \RemoveEmptyStaves (Frenched score).

\score {
  <<
    \new Staff {
      s1*0^"Marks are not above the score"
      \music
    }
    \new StaffGroup {
      <<
        \new Staff \with {
          \consists "Mark_engraver"
        } {
          s1*0^"Marks are above this Staff"
          \music
        }
        \new Staff {
          \music
        }
      >>
    }
  >>
  \layout {
    \context {
      \Score
      \remove "Mark_engraver"
      \remove "Staff_collecting_engraver"
    }
    \context {
      \Staff
      % \consists "Mark_engraver"
      % We add this engraver to the second Staff only
      \consists "Staff_collecting_engraver"
    }
  }
}

%%%% End of the snippet
~~~~


---

Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto
    • ... Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development

Reply via email to