Re: When to use overrideProperty instead of override?

[Trevor Bača]

On 12/30/05, Han-Wen Nienhuys <address@hidden> wrote:
> Trevor Bača wrote:
> > Seems like
> >
> >     \overrideProperty
> >     #"Score.NonMusicalPaperColumn"
> >     #'line-break-system-details
> >     #'((fixed-alignment-extra-space . 15))
> >
> > works great, but that
> >
> >     \override Score.NonMusicalPaperColumn #'line-break-system-details
> > = #'((fixed-alignment-extra-space . 15))
> >
> > is silent.
> >
> >
> > Question: what's the intent of \overrideProperty? (Ie, when's the
> > right time to use \overrideProperty instead of \override?)
>
> \override changes the initialization of a Grob. Since
> Score.NonMusicalPaperColumn grobs are created and initialized before a
> normal \override is processed, it has no effect on
> Score.NonMusicalPaperColumn doesn't work.

OK.

So summary: use \override for overriding almost all grob properties;
use \overrideProperty only for properties belonging to those few grobs
like Score.NonMusicalPaperColumn that are created *prior to* normal
\override processing.

Thanks for the explanation.


--
Trevor Bača
address@hidden