[EMAIL PROTECTED] writes: > > necessary? If not, then we can skip that option, and simply never > > merge if styles are different. > > I considered that, but I saw the pattern for different heads and > different dottings. Not having much choral experience (where I > suspect this comes into play), I don't see a lot of reason for those > properties, either, but lilypond provides them. So I figured I'd > also provide a mechanism for the existing behavior as part of my > fix. I was just trying to leave as much flexibility in
The other properties reflect some guitar and piano practices. I don't see use of a merge-different-style, so please leave it out for now. We can always put it back in later. > function, and used it for my patch, too. > > I have been playing around the last couple of weeks with the autochange function > (also for use with handbells - expect a patch in a couple of days), and I've > been learning quite a bit about object and context properties. I now would use > the property directly, but I didn't realize how it all fit together when I wrote > this patch. I haven't integrated your previous patch due to the questions I had. Could you (re)implement the functionality as you would do it now, and send me the patch, so I can apply it to the CVS repo? Thanks! -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen _______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
