Re: Some things need need to be fixed on the interfaces pages

[Christopher Heckman]

On Thu, Dec 12, 2024 at 4:05 PM David Kastrup <dak@gnu.org> wrote:
>
> Christopher Heckman <christopher.heckman@asu.edu> writes:
>
> > On Wed, Dec 11, 2024 at 10:58 PM Werner LEMBERG <wl@gnu.org> wrote:
> >>
> >> >> IIRC, a suggestion in the mentioned thread is to make the property
> >> >> description displayed for a given grob show which interfaces it is
> >> >> part of, for example
> >> >>
> >> >> ```
> >> >> ‘spacing-pair’ (pair)
> >> >>      interface(s):
> >> >>           centered-spanner-interface, multi-measure-interface
> >> [...]
> >> >>      default value:
> >> >>           '(break-alignment . break-alignment)
> >> >>
> >> >
> >> > There's a problem there, too, in that the default value depends on the 
> >> > grob.
> >> >
> >> > In MeasureSpanner, the default value is (staff-bar . staff-bar)
> >> >
> >> > In PercentRepeat, it's (break-alignment . staff-bar)
> >>
> >> I don't see a problem here.
> >
> > You can't talk about *the* default value, because it's not unique; you
> > can only talk about *a* default value.
>
> I think you are confusing value and default value.  The default value is
> what is being used unless overriden by grob definition or context
> definition or user.  Many grob definitions override the default, and
> several context definitions also apply overrides.  Only then does the
> user come into play.
>
> > The default values seem to be set in grobs, not interfaces, so as an
> > alternative, how about something like ...
>
> Again: you are confusing what "default" means in this context.  The
> grobs can override the defaults.
>
> --
> David Kastrup

Okay, I think I see what's going on; the interfaces set values, then
the Grobs set values, then specifics are set, in that order. When the
Grob sets the value, you're calling that an "override"; I consider it
to still be part of the "default" values.

In the Internals section of lilypond.org, the default values of
properties are largely listed on the grob pages, not on the interface
pages, which is what I was going by.

As it turns out -- correct me if I'm wrong -- the interfaces don't set
too many default values, mostly "pointer intialization" or "behind the
scene" work, but they always get to be first.

And getting back to the topic at hand, I still think that the
*overriden* values should be listed for each Grob should be listed for
each property, because that would be one less mouse click.

==================================
Christopher Carl Heckman
Honors Faculty
Teaching Associate Professor
33° 25' 7'' N, 111° 55' 55'' W
ECA 212
School of Mathematical & Statistical Sciences
Arizona State University (T1N R4E Sect22 NW1/4)
Tempe, AZ 85287 - 1804
United States of America
North America
Planet Earth
Solar System
Gould Belt
Local Bubble
Local Fluff
Milky Way Galaxy, Orion Arm
Local Group
Virgo Supercluster
Pisces-Cetus Supercluster Complex
Universe
Multiverse
==================================