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

range selection lost on adding section break, if clef change is there #25902

Open
4 tasks done
sammik opened this issue Dec 22, 2024 · 0 comments
Open
4 tasks done

range selection lost on adding section break, if clef change is there #25902

sammik opened this issue Dec 22, 2024 · 0 comments
Labels
P3 Priority: Low regression MS4 Regression on a prior release UX/interaction

Comments

@sammik
Copy link
Contributor

sammik commented Dec 22, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

  1. select range selection, which end in place of clef change
  2. add section break
  3. see - range selection is lost, clef in next measure is selected instead

Supporting files, videos and screenshots

range-lost-section.mp4

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

master nightly

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Linux Mint (Ubuntu 22.04)

Additional context

No metter, if courtesy clef is on, or off.

Regression:
Works in 4.0.2
Doesnt work in 4.1.0

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
@muse-bot muse-bot added regression MS4 Regression on a prior release UX/interaction labels Dec 22, 2024
@bkunda bkunda moved this to Next one or two releases in MuseScore Studio Backlog Dec 27, 2024
@bkunda bkunda added the P3 Priority: Low label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Priority: Low regression MS4 Regression on a prior release UX/interaction
Projects
Status: Next one or two releases
Development

No branches or pull requests

3 participants