On 29 July 2010 20:34, Mike Solomon <mike...@ufl.edu> wrote: > I think that this patch is the easiest way to assure that the break > processing will happen when do_break_processing is called (although I could > be wrong), whereas creating a grob doesn't get you a spanner's break > processing.
Have you looked at the macros which creates each type of grob? All they do is call the same internal function (internal_make_grob), then check validity using dynamic_cast. Each type of grob gets the correct properties/interfaces/class initialized from the description in all-grob-descriptions, so I can't see why there would be any problems later on with break processing. Cheers, Neil _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel