Confirmed. In the code, fingerings are laid out first, then the tuplet, so in theory this would work, but the tuplet bracket & number don't pay attention to fingerings - just the chord itself. There is an algorithm not dissimilar to that for slurs in principle but without the autoplace component that uses the shape of the bracket to check for collisions.
For the record, my fingering layout PR https://github.com/musescore/MuseScore/pull/4591 does not address this, because the tuplet layout code itself does not seem to account for fingerings even though they are in the skyline.
Comments
Confirmed. In the code, fingerings are laid out first, then the tuplet, so in theory this would work, but the tuplet bracket & number don't pay attention to fingerings - just the chord itself. There is an algorithm not dissimilar to that for slurs in principle but without the autoplace component that uses the shape of the bracket to check for collisions.
Still the case in RC.
Indeed, Implementing slur-like collision detection for tuplets is non-trivial, it won't happen in the next few days.
For the record, my fingering layout PR https://github.com/musescore/MuseScore/pull/4591 does not address this, because the tuplet layout code itself does not seem to account for fingerings even though they are in the skyline.
Autoplace for tuplets is now implemented, and they are placed outside fingerings and articulations.
Automatically closed -- issue fixed for 2 weeks with no activity.