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

System markings: Re-enable Add > System marking after deleting one #26668

Open
4 tasks done
avvvvve opened this issue Feb 21, 2025 · 0 comments
Open
4 tasks done

System markings: Re-enable Add > System marking after deleting one #26668

avvvvve opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
community Issues particularly suitable for community contributors to work on P3 Priority: Low Pre-release feature issue This pertains to a new feature and should be addressed prior to release UX/interaction

Comments

@avvvvve
Copy link

avvvvve commented Feb 21, 2025

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

This PR added handling that disables the Layout > Add > "System marking..." option when there are as many system markings as there are instruments in the score.

However, when you delete a system marking, the button does not become re-enabled immediately until you click another instrument/system marking row in the Layout list.

It should be re-enabled immediately

Supporting files, videos and screenshots

Screen.Recording.2025-02-21.at.5.30.43.PM.mov

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

#26653 (Nightly build once this is merged)

Regression

No.

Operating system

macOS 15

Additional context

No response

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
@avvvvve avvvvve added community Issues particularly suitable for community contributors to work on P3 Priority: Low Pre-release feature issue This pertains to a new feature and should be addressed prior to release labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Issues particularly suitable for community contributors to work on P3 Priority: Low Pre-release feature issue This pertains to a new feature and should be addressed prior to release UX/interaction
Projects
Status: Available
Development

No branches or pull requests

3 participants