slurs too high, outside staff

This is an unfortunate but known limitation of the current algorithm for slur autoplace. We look pretty carefully for collisions (in this case, I suspect the G# reads as a collision because we are checking the "bounding box" of the sharp sign) to avoid having to move the slur at all). But if we do decide we need to move, unfortunately the only way we have to figure out how far it needs to be moved requires moving it outside the staff completely. This is not good indeed, but that's the best we can do at the moment the way our data structures are set up. Hopefully we will find a way around this at some point. That and coming up with a way to make slurs more bowed if need be rather than just taking the default "flat" slur and moving it up would be the main two enhancements I still want to see.

https://github.com/musescore/MuseScore/pull/4750

The score attached reports as corrupt in master due to that very tuplet (presumably something to do with the new fractions code, either catching real corruptions we missed earlier, or causing new problems). But recreating that measure in a new score, with my PR, yields this:

Fixed in branch master, commit 8ee73c6d14

fix #280466: slurs avoid staff when autoplaced

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