Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob

[lilypond]

Updates:
        Labels: -Priority-High Priority-Medium

Comment #11 on issue 1063 by address@hidden: Reverting nested property fails  
to restore default value if preceded by override in same grob
http://code.google.com/p/lilypond/issues/detail?id=1063

Ok, I am basically more or less through with trying to find an approach for  
tackling this.  What I'll basically do is to maintain sort of a master data  
structure for nested overrides that has SCM_UNDEFINED in all leaves that  
are not actual overrides and thus should be filled in from parenting  
contexts.  When the alist needs regeneration in updated_grob_properties, a  
shadow is generated with all SCM_UNDEFINED being replaced by the respective  
properties of contexts in the ancestry.

It is not all too clear how to maintain the stack-like behavior of  
override/revert when the depth of the specified nesting is not matched and,  
say, you have something like

override a ... revert a.b ...

I'll see where this approach will get me.

I am downgrading the importance since the problem is basically back to  
before the decision "is the complexity of nested property access worth the  
cost?" and there is not yet working code available that can be used for  
answering that question.