You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While a good graphical solution, representing this single StaveNote as two independent StaveNotes puts a big burden on Voice construction by requiring extra voices with complementary GhostNotes.
In my experience, a cross-staff chord is not a particularly more complicated case than a single staff chord -- the codepath for both would ideally be nearly, if not completely, identical. Noteheads already have a setStave method, which is set to the same stave as the parent StaveNote when setStave is called. There's also logic in places that assume that all noteheads are on the same staff, but taking into account potentially different staves doesn't complicate things much.
I'd guess that if stems were a bit bit smarter, formatting occurred in consistent parts of the lifecycle, and the StaveNote delegated to the stem and noteheads wherever possible (ie: deprecate staveNote.ys), then this should be straightforward to support.
The text was updated successfully, but these errors were encountered: