On measure-append, a final barline shouldn’t always be added to the end of the score

[Riley-Sullivan]

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

This one is a bit hard to describe, but it appears that when you append measures to the score, MuseScore puts a final barline at the end of the score in some cases but not in others.

For example, it doesn’t appear to when there already is a final barline on a new score (which makes sense), but if you replace it with a manually-added final barline, it adds another final barline even though there already is one there (it was there because you added it). In this case there are two final barlines: on the second last measure the one you added, and on the very last measure the one MuseScore added.

By the way, if you instead change the final barline to a double barline (for example), the issue becomes clearer: your double barline is there as well as MuseScore’s final barline.

So I assume this is really two issues in one, or at least it has two causes:

1. On appending measures, a final barline is consistently added to the last measure even if it’s been deleted.
2. A manually-added final barline is not really seen as a true final barline, or at least MuseScore doesn’t see it the same as the final barline that was there in the new default score.

Watch the attached screen recording for the best demonstration that I could think of.

To reproduce
Steps to reproduce the behavior.

1. Make a new score and delete the final barline.
2. Manually add a final barline to the last measure.
3. Append a measure to the end of the score (for example, using Command B).
4. See error: there are now two final barlines (one on each of the last two measures), instead of just one.

Supporting files, videos and screenshots

Screen.Recording.mov

What is the latest version of MuseScore Studio where this issue is present?

4.4.2

Regression

No.

Operating system

macOS 12.7.2

Additional context

This began in MS3, and was not present in MS2.

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible