Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems adding key signatures to a range #23936

Closed
4 tasks done
oktophonie opened this issue Aug 6, 2024 · 1 comment · Fixed by #24205
Closed
4 tasks done

Problems adding key signatures to a range #23936

oktophonie opened this issue Aug 6, 2024 · 1 comment · Fixed by #24205
Assignees
Labels

Comments

@oktophonie
Copy link
Contributor

oktophonie commented Aug 6, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

Normally, adding a key signature to a range will add the change at the start of the range, and 'cancel' it (reverting to whatever key signature was previously in force) at the end. For example, starting with this:
image

If we add a D major key sig to the selected range, we get:
image

Which seems fair enough.

However, if there is already a key signature change at the end of the range, it will be overwritten. So this:
image

Becomes this (overwriting the Ab with Bb):
image

A fun exception: in this same situation, if you replace the range with the same key signature that is already there, then the key sig change at the end of the range is just deleted. So this:
image

Becomes this (if you apply D major):
image

It gets worse. If you try doing this repeatedly it'll get even more random, and sometimes I see the key signatures get shifted by a bar. The horror ... the horror ...

Supporting files, videos and screenshots

See above

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

3.6 (at least) up until master

Regression

No.

Operating system

Linux (but presumably any)

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
@oktophonie oktophonie assigned miiizen and oktophonie and unassigned oktophonie Aug 6, 2024
@oktophonie oktophonie added P1 Priority: High P2 Priority: Medium and removed P1 Priority: High labels Aug 6, 2024
@sammik
Copy link
Contributor

sammik commented Aug 12, 2024

Same happens to clefs and time signatures too.

(And after undo, range selection is extended by one measure #17718)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment