musescore / musescore/MuseScore
Set default visibilty in text styles
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Your idea
Add a 'visible' setting to text styles, to control whether different types of text appear in different scores/parts.
There is a workaround for this - you can make text invisible in a style by setting the alpha in the colour settings to zero. However, this makes the text fully invisible - not the greyed-out kind of invisible that you get when 'visible' is unticked - and therefore impossible to click on them once the colour has been set.
Problem to be solved
I have two main style templates I use - one for full scores, and one for parts. In these, I've set up several user text styles, for various different types of text used in my scores.
I would like to be able to use these text styles to control default visibility. For instance - there are certain types of text that I want to appear in parts, but not in the full score. If text styles included a 'visible' tickbox, I could set them to invisible in full score style, and keep them visible in the parts style.
Prior art
No response
Additional context
No response
Checklist
- This request follows the guidelines for reporting issues
- I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
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.
Research direction
No files or tests are named. Start by locating text-style settings and the existing per-element Visible control, then compare how full-score and part style templates are applied. Done means a text style can store a default visibility value independently of alpha, with different score and part templates applying it consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100