[EMAIL PROTECTED] writes:
> >mutopia/J.S.Bach/wtk1-fugue2 for examples. It is conceivable to have
> >such pieces where multiple slurs cross staffs and not follow any
> >nesting rules.
>
>
> Yes, I have, and the Bach fugues are an excellent example of polyphonic
> music. However, I was simply going by the example you gave, and that didn't
> seem to present any problem that couldn't be solved simply. Is there an
> example in the fugue of which you speak of multiple slurs crossing staves?
No, but I don't see why this could not happen. I am sure you can find
it ni the more intricate late-romantic piano music.
> >has to `know' that a note is there. Knowing that notes are there is
> >also done using notation contexts.
>
>
> Again, as you've pointed out, I'm mostly ignorant of the implementation of
> the various contexts. However, it seems like it would be a fairly simple
> fix by restricting this type of activity to certain staff contexts, e.g.,
> the PianoStaff context. You could treat it as a single entity with 11 lines
> (by merging the two separate staves that make up the PianoStaff), for
> example. Lily seems to handle these problems within a single staff quite
> well as it is, wouldn't you agree? Why would it not be possible to extend
> that idea to a special staff system (again, such as the PianoStaff)?
PianoStaff is just two normal staffs stacked together at a fixed
distance. If you think this is not The Way It should be, then you're
probably right, but I want the normal Staff code to be shared with
the Staff-in-PianoStaff code. You can't build the slur functionality
at Staff level or PianoStaff level, because that slur would see all notes
from all voices in the said staff/pianostaff.
> >I am not trying to tear *you* down. It's just that you have no idea
> >how Lily works, so your implementation suggestions are quite useless
> >to me. :)
>
>
> In that case, you could simply tell what is and isn't possible, and then I
> would be able to give you workable implementation suggestions. ;-)
I'd love to, but my experience that the more explanation people want,
the less likely they'll send a patch or come up with good
suggestions. Most of the patches I get are made without me explaining
how they should work. So (hoping to receive a patch) I'll leave at this
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
