On Sat, Mar 26, 2011 at 6:28 PM, <mts...@gmail.com> wrote: > Reviewers: , > > Message: > I think this is a better approach to getting beam collision resolution > out of auto-beams.
Quick comment: I'd say that timestep-count as a property is not necessary. The 'width' of an autobeam could also be garnered by looking at its bounds, eg beam->get_bound(LEFT)-> get_column(). From the column you could either look at rank or when. A completely different approach now comes to mind: there is no strict need to do all this processing 'on-line'. You could also have the engraver collect a list of grobs + timing-ranges in a list. In finalize(), you could sort the list, and decide which grobs to add where. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
