>> A warning message would be printed, possibly along the lines of
>>
>> overriding property `stencil' for grob `BarLine' has no effect in
>> context `Voice'
>
> I would like to state that I consider that a step in the wrong
> direction. If we make Lilypond smart enough to figure out what is
> wrong, we should use that smartness for doing the right thing
> instead of educating the user.
>
> Lilypond once had subvoices (threads?). They have been eliminated,
> as far as I understand, because they were causing more confusion
> than good, and an elemental part of that confusion was that they
> made it harder to figure out just what context you wanted to be
> setting your properties for.
>
> If we give Lilypond that knowledge, then we should make it pick the
> right context itself.
Hmm. You mean that a user should never need to specify the context of
a grob, and lilypond should be able to automatically walk over all
contexts to find the right one? This sounds useful. And, similar to
languages like C++, it should be possible to explicitly select the
context in case there is ever a situation where this is necessary $(Q#|(B
currently, I'm not aware that an engraver can be part of two contexts
at the same time, but...
Werner
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
