Re: Collision problem when using \stopStaff and \startStaff

[Thomas Morley]

2012/10/5 TaoCG <address@hidden>:
> I currently have to typeset a lot of this:
> skipgliss.png
> <http://lilypond.1069038.n5.nabble.com/file/n134155/skipgliss.png>
>
> The problem is when I use stop and startStaff to hide the ledgerlines the
> dynamics and tupletbracket both move as close to the staff as possible and
> collide like you see in the image.
>
> Here is the lily code. When you comment out the stop- and startStaff
> commands the bracket and dynamics move to its proper place.
>
> \version "2.16.0"
>
> skipGlissOn =
> {
>     \override NoteColumn #'glissando-skip = ##t
>     \override NoteHead #'transparent = ##t
>     \stopStaff
>     \override Staff.LedgerLineSpanner #'transparent = ##t
>     \startStaff
> }
>
> skipGlissOff =
> {
>     \revert NoteColumn #'glissando-skip
>     \revert NoteHead #'transparent
>     \stopStaff
>     \revert Staff.LedgerLineSpanner #'transparent
>     \startStaff
> }
>
> \relative c'
> {
>     \dynamicUp
>     \times 8/10 { c32\pp\>\glissando \skipGlissOn c c c b b b b
> \skipGlissOff b\! r }
> }
>
>
>
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/Collision-problem-when-using-stopStaff-and-startStaff-tp134155.html
> Sent from the User mailing list archive at Nabble.com.
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user

No need for \startStaff and \stopStaff.
Why not simply
\override NoteHead #'no-ledgers = ##t
But not tested.

HTH,
  Harm