Re: [Lilypond-auto] Issue 3731 in lilypond: Patch: Adds outside-staff-interface and outside-staff-axis-group-interface

[lilypond]

Comment #8 on issue 3731 by address@hidden: Patch: Adds  
outside-staff-interface and outside-staff-axis-group-interface
http://code.google.com/p/lilypond/issues/detail?id=3731

The cell differences in the regtests seem to be the usual give-and-take  
when new regtests are added, resulting in a different distribution of the  
other tests among processes.

I'm basically for moving to a state where a grob keeps its data in arrays  
rather than property lists, and so a grob should have a well-defined set of  
accessible properties and interfaces.

I'm just not overly convinced that "outside-staff-interface" makes a good  
category.  Basically pretty much everything that is not an integral part of  
the staff itself (like staff lines, time signature, clef) can be  
placed "outside" of the staff.

I'm even more skeptical about the outside-staff-axis-group-interface since  
I can't offhand name a single axis group where the kind of vertical  
arrangement that the outside-staff-interface is for would never be wanted.

So shouldn't those elements be part of vertical-axis-group-interface (or  
was that axis-group-interface?) rather than creating another interface for  
them?

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings