(ly:grob-layout grob) 'staff-space))
(staff-line-thickness
(ly:output-def-lookup (ly:grob-layout grob) 'line-thickness))
- (grob-name (lambda (x) (assq-ref
- (ly:grob-property x 'meta) 'name)))
(par-x (ly:grob-parent grob X))
- (dyn-text (eq? (grob-name par-x) 'DynamicText ))
+ (dyn-text (grob::has-interface par-x 'dynamic-text-interface))
(dyn-text-stencil-x-length
(if dyn-text
(interval-length
+++ /dev/null
-%% DO NOT EDIT this file manually; it is automatically
-%% generated from LSR http://lsr.di.unimi.it
-%% Make any changes in LSR itself, or in Documentation/snippets/new/ ,
-%% and then run scripts/auxiliar/makelsr.py
-%%
-%% This file is in the public domain.
-\version "2.18.0"
-
-\header {
- lsrtags = "contexts-and-engravers, text, tweaks-and-overrides"
-
- texidoc = "
-For technical reasons, text scripts attached to note heads cannot
-easily be centered on a note head's width, unlike articulations.
-
-Instead of using trial-and-error offset tweaks, this snippet uses a
-Scheme engraver to reset the horizontal parent of each markup to a
-@code{NoteColumn}. This also allows text to follow note heads which
-have been shifted via @code{force-hshift}.
-
-
-
-"
- doctitle = "Centering markup on note heads automatically"
-} % begin verbatim
-
-#(define (Text_align_engraver ctx)
- (let ((scripts '())
- (note-column #f))
- (make-engraver
- (acknowledgers
- ((note-column-interface trans grob source)
- ;; cache NoteColumn in this Voice context
- (set! note-column grob))
- ((text-script-interface trans grob source)
- ;; whenever a TextScript is acknowledged,
- ;; add it to `scripts' list
- (set! scripts (cons grob scripts))))
- ((stop-translation-timestep trans)
- ;; if any TextScript grobs exist,
- ;; set NoteColumn as X-parent
- (for-each (lambda (script)
- (set! (ly:grob-parent script X) note-column))
- scripts)
- ;; clear scripts ready for next timestep
- (set! scripts '())))))
-
-\layout {
- \context {
- \Voice
- \consists #Text_align_engraver
- \override TextScript.X-offset =
- #ly:self-alignment-interface::aligned-on-x-parent
- \override TextScript.self-alignment-X = #CENTER
- }
-}
-
-\new Staff <<
- \relative c'' {
- \override NoteColumn.force-hshift = #3
- c1-\markup { \arrow-head #Y #DOWN ##t }
- }
- \\
- \relative c' {
- a4 a-\markup { \huge ^ } a a
- }
->>
adding-an-extra-staff.ly
automatically-changing-the-stem-direction-of-the-middle-note-based-on-the-melody.ly
centered-measure-numbers.ly
-centering-markup-on-note-heads-automatically.ly
changing-midi-output-to-one-channel-per-voice.ly
changing-time-signatures-inside-a-polymetric-section-using--scaledurations.ly
chant-or-psalms-notation.ly
\once \override Accidental.extra-offset = #'(4 . -.1)
}
+
\relative c' {
<< { \fixA <b d!>8 } \\ { \voiceThree \fixB dis } >> s
}
texidoc = "
When working with grob callbacks, it can be helpful to understand a
-grob's @qq{ancestry}. Most grobs have @qq{parents} which influence the
+grob’s ancestry. Most grobs have parents which influence the
positioning of the grob. X- and Y-parents influence the horizontal and
vertical positions for the grob, respectively. Additionally, each
parent may have parents of its own.
-Unfortunately, there are several aspects of a grob's ancestry that can
+Unfortunately, there are several aspects of a grob’s ancestry that can
lead to confusion:
-* The types of parents a grob has may depend on context. * For some
-grobs, the X- and Y-parents are the same. * A particular @qq{ancestor}
-may be related to a grob in multiple ways. * The concept of
-@qq{generations} is misleading.
+
+* The types of parents a grob has may depend on context.
+
+* For some grobs, the X- and Y-parents are the same.
+
+* A particular “ancestor” may be related to a grob in multiple ways.
+
+* The concept of “generations” is misleading.
For example, the @code{System} grob can be both parent (on the Y-side)
grob.
-This macro prints (to the console) a textual representation of a grob's
+This macro prints (to the console) a textual representation of a grob’s
ancestry.
+When called this way:
-When called this way
-
-
-@{
- \\once \\override NoteHead #'before-line-breaking = #display-ancestry
- c @}
-
+@code{@{ \\once \\override NoteHead.before-line-breaking =
+#display-ancestry c @}}
The following output is generated:
-------------------------------------
-
-NoteHead X,Y: NoteColumn
- X: PaperColumn
- X,Y: System
- Y: VerticalAxisGroup
- X: NonMusicalPaperColumn
- X,Y: System
- Y: VerticalAlignment
- X: NonMusicalPaperColumn
- X,Y: System
- Y: System
-
-
+@code{NoteHead X,Y: NoteColumn
+ X: PaperColumn
+ X,Y: System
+ Y: VerticalAxisGroup
+ X: NonMusicalPaperColumn
+ X,Y: System
+ Y: VerticalAlignment
+ X: NonMusicalPaperColumn
+ X,Y: System
+ Y: System}
"
doctitle = "Displaying grob ancestry"
<bs' fs'>2
e'2
|
- <b'! a'>2 -\tweak #'style #'none \cresc
+ <b'! a'>2 -\tweak style #'none \cresc
b'4
<e'' cs''>4
|
\key c \major
\relative c''
{
- % disable the following line to see the noteheads while writing the song
+ % disable the following line to see the the noteheads while writing the song
\NoNoteHead
\override NoteHead.no-ledgers = ##t
aligning-syllables-with-melisma.ly
blanking-staff-lines-using-the--whiteout-command.ly
center-text-below-hairpin-dynamics.ly
-centering-markup-on-note-heads-automatically.ly
changing-ottava-text.ly
changing-the-default-text-font-family.ly
combining-dynamics-with-markup-texts.ly
asymmetric-slurs.ly
avoiding-collisions-with-chord-fingerings.ly
caesura-railtracks-with-fermata.ly
-centering-markup-on-note-heads-automatically.ly
changing-a-single-notes-size-in-a-chord.ly
changing-beam-thickness-and-spacing.ly
changing-form-of-multi-measure-rests.ly
MensStyle = {
\autoBeamOff
- \override NoteHead #'style = #'petrucci
- \override Score.BarNumber #'transparent = ##t
+ \override NoteHead.style = #'petrucci
+ \override Score.BarNumber.transparent = ##t
\override Stem.neutral-direction = #up
}
projects / lilypond.git / commitdiff