Re: [Gnu-music-discuss] Missing legal.ly, beam questions, padding...

[Scott Ballantyne]

From: Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:

> [EMAIL PROTECTED] writes:
> > You could set the property separately for the different
> > staff lines (hope you don't have too many clef changes 
> > in the parts). Of course, Lilypond should take the 
> > clef into account when it calculates the spacing.
> 
> I'm not sure if that's a very good solution: storing pointers to the
> clefs will cost a fair amount of memory, especially on large scores
> (roughly #staffs * #measures * 24 bytes). Maybe we should just
> increase the default padding?
> 

Why can't the bounding box, or whatever it's called in metafont,
simply be used when type setting the bar numbers? Or for that matter,
placing marks above or below the staff?

I realize this is probably naive, but it does seem like the right
answer.

sdb
-- 
[EMAIL PROTECTED]
_______________________________________________
gnu-music-discuss mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/gnu-music-discuss