lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffG


From: lilypond
Subject: Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes
Date: Sat, 22 Dec 2012 23:17:51 +0000


Comment #26 on issue 2990 by address@hidden: \RemoveEmptyStaves in StaffGroup context crashes
http://code.google.com/p/lilypond/issues/detail?id=2990

Now we're talkin'
I think some sort of efficiently implemented tree would be a great idea. The issue is that there are a few levels of data to hack trough. Grob arrays contain grove, which have properties, which themselves may be Grob arrays. So, one still needs to pass through the property or object lookup mechanism. If there is a way to implement a tree data structure while preserving the core Grob/property model, I'm all for it.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]