Re: access font-size of clef G_8

[David Kastrup]

Noeck <address@hidden> writes:

> Thanks David for the explanation! The first part is clear now.
>
>> Also a) changes a single context definition while b) changes all context
>> definitions that have an alias of "Score" as well (for "Score" that's
>> rather unlikely, but for "Staff" there are a lot more candidates).
>
> That's interesting, I tested with a VaticanaStaff
> \context { \Staff \override StaffSymbol.color = #green } % no changes
> \override Staff.StaffSymbol.color = #blue  % changes the VaticanaStaff
> as you described.
>
>>> And does this difference change anything if it is put in a global
>>> (i.e.  score-wide) \layout block?
>> 
>> No.
>
> Sorry for being unclear. I wanted to ask: Does the following difference
> between changes on Score and Staff level change anything if put in a
> global \layout block?
>
>>> 1)  \override Score.ClefModifier.font-size = #2
>>> 2)  \override Staff.ClefModifier.font-size = #2

Sorry, but the question is nonsensical.  "Does the following difference
between changes [...] change anything if [...]".  Please make up your
mind about what question you want to ask.  What "difference between
changes"?  How does a "difference [...] change anything"?

>>> 1) Changes all clef modifiers in the whole score and 2) in every
>>> staff in the score. As the clef modifier occurs in a staff, this
>>> sounds identical to me. Are there situation where the effect
>>> differs?
>> 
>> Depends on the context definitions in ly/engraver-init.ly.  Does not
>> appear like ClefModifier is touched there (after initializing it in
>> Global from all-grob-descriptions).
>> 
>> So any such situation will be created by yourself.
>
> Could you tell me what such a situation would be (ClefModifier is just
> an example) for any grob in any context? When would there be a
> difference? I still can't see it.

Grob properties are inherited through the context hierarchy.  An
engraver acting in a particular context will see properties set in this
context.  If they aren't set there, it will consult the parent context
recursively.

-- 
David Kastrup