Re: [Lilypond-auto] Issue 4131 in lilypond: Patch: Reimplement forced partcombine decisions via context properties

[lilypond]

Comment #19 on issue 4131 by address@hidden: Patch: Reimplement  
forced partcombine decisions via context properties
https://code.google.com/p/lilypond/issues/detail?id=4131

> Putting the chord range in a property would seem to make it reasonably  
> easy to follow the same strategy for getting the information out from a  
> property as it is done in this patch.

This is the sense in which it is blocking me.  I'll be working in the same  
area, doing a similar task, and I want my part-time, late-night effort not  
to be any more complicated than it has to be.  (Understand I'm not  
complaining.)

If you'd really rather not push this patch, I could still refer to it as an  
example of how to read properties in the part combiner; but if you're  
comfortable pushing it now, that would be great.  I want to follow an  
approved strategy, and seeing a precedent right before my eyes is more  
comfortable.  Thanks.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings