Notes collide between cross-staff

Came up again in https://musescore.org/en/node/187716

And this isn't just a 2.0.3 issue, but happens with 2.0.0 too.
And 1.3 thru 1.0 too (good to have all the portable apps handy), so probably this never worked properly.

In master currently this doesn't work at all, now reported in #187891: Cross staff notation doesn't work, shows notes in wrong (origin) staff at wrong (same as target) position

FWIW, there is one possible justification for this behavior: the use of cross staff notation to "fake" certain effects involving single chords that span two staves and wanting the heads to overlap. I know, that sounds kind of vague, but I do remember at one point someone showing a use a case where we would want the cross staff notes to not affect spacing. Not saying this in itself is reason not to change the behavior, just pointing it out. Whatever the case was I am remembering, chances are it could be addressed by making sure we continue to overlap if one notehead is hidden.

Cool, I see the crash on opening so the file is not opened at all.

Crash in nightlies I meant. MuseScoreNightly-2018-03-30-2123-master-b92a6e0.dmg (MacOS)

It is not a 3.0 issue though, but affects all releases so far. The crash on open in 3.0 seems new, so should be a different issue. #187891: Cross staff notation doesn't work, shows notes in wrong (origin) staff at wrong (same as target) position doesn't talk about a crash either, but at least is master only

Came up again https://musescore.org/en/node/271336

1. Open attached score (produced in 2.3.2).

Expected result (from LilyPond 2.18.2):

Actual result:

Note: Unison notes also affected, not just adjacent ones.

Using MuseScore 2.3.2 and 3.0 Nightly 8366ff1 - Mac 10.11.6.

Relates to #285233: [EPIC] Cross-staff notation issues

Are y'all still over this right now? I think this is a rather serious issue especially for piano composers and transcribers. I know y'all aren't. Have you thought of fixing that in the stable release-- not have thought, HAVE...

This is definitely the sort of thing that we would like to be able to address the next time we make any significant changes to the layout algorithm, There is a decent chance that would happen for MuseScore 4.

Okay, at least there IS a way to set it manually.

Came up again in https://musescore.org/en/node/319520

See https://github.com/musescore/MuseScore/issues/20104

Allegedly fixed in 4.2

Automatically closed -- issue fixed for 2 weeks with no activity.