musescore / musescore/MuseScore
Anchor overlay color should take into account paper color
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UI bug (incorrect info or interface appearance)
Description with steps to reproduce
This is about the colored stripes shown on the score when repositioning dynamics/lines using the Shift + Arrow key shortcuts introduced in 4.4.
They are meant to look like they are semitransparent overlays beneath the score. This is working correctly when the score page color (Preferences > Appearance) is the default, but when the score is inverted or set to another color, the overlay still looks as if it had a white background behind it.
@mike-spa implemented this by running a calculation using the page color, but I'm guessing that was hard-coded instead of pulling from the page color set in preferences.
However, simply using the same transparency values on a dark background renders the stripes nearly invisible (see screenshot below). So if we want to do this right, we should use a smarter color calculation to make stripes brighter on backgrounds darker than a certain value.
Supporting files, videos and screenshots
Example on inverted background
https://github.com/user-attachments/assets/b288d728-ec06-4799-9eba-d8ea1366df5a
Example on color background
https://github.com/user-attachments/assets/9a12ea4d-12a9-4fde-b5e3-3c7443d2b451
What is the latest version of MuseScore Studio where this issue is present?
Nightly
Regression
No.
Operating system
macOS 14.5
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.