[EPIC] Cross-staff notation issues

• Mar 2, 2019 - 17:14
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
Tags

Issues relating to cross-staff notation:

#284682: Position offset when moving cross-beam notes with the mouse
#280531: Beam separates from stems when crossing staves.
#279182: Cross-staff slurs/ties trying to avoid note on wrong staff
#280969: Cross staff 8ths lose beam if all notes moved to staff above
#282443: Incorrect behavior of a cross-staff measure rest
#279736: Cross-staff note offset to align with note in original staff
#114141: Notes collide between cross-staff
#187891: Cross staff notation doesn't work, shows notes in wrong (origin) staff at wrong (same as target) position
#43936: Beam and stem of cross-staff notes don't flip
#118656: Cross-staff slur missing or incorrect when a part is created
#103681: Cross-staff slur is copied even when end anchor is not copied
#54366: cross-staff notes ignore accidentals
#21990: Dragging stave with cross staff beaming produces remnants
#20836: Notes too close when crossing staves

Not all of these are regressions, nor even confirmed to still exist in 3.0 currently. But the issue with beams disappearing and slurs attaching incorrectly are real and critical.

FWIW, I didn't bother listing issues involving import of 1.3 scores into 2.x :-)

Some interesting suggestions for extending this facility:

#110611: split chord across staves
#280156: Add a way to move elements other than notes cross-staff (or do it automatically when notes are moved)
#65806: Cross-Staff and Cross-Voice Arpeggio
#14687: Cross-staff notation within one voice; beam multiple notes across staves with selection
#110906: beam across hidden staves of a grand staff
#40391: Stem direction of cross-staff notes incorrect