On Sat, Mar 26, 2011 at 6:54 PM, m...@apollinemike.com <m...@apollinemike.com> wrote:
>> 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. > This sounds like a great idea. Do you have time to write something along > those lines? Unfortunately, no. -- 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
