musescore / musescore/MuseScore
Adding options for automatic placement of the glissando line and clarifying text
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
- When the distance between the notes for the glissando line is too small, it should not be pushed there with tension, instead it should be moved above (or below, depending on the vertical position of the pitch) of the staff. In this case, the clarifying text should be indicated and placed on the same diagonal as the glissando line.
- In the glissando properties, the text should be able to be entered in 2 lines. Besides the word "gliss." there are many other clarifying texts to this instruction, for example: harm., chrom., white-keys, strum across strings, etc., and putting this clarifying text on one line is too tight and difficult to read from the point of view of one-line writing.
- The glissando line itself is very mysterious. It seems to be narrow, but the invisible area of its capture is so wide that it does not allow me to edit other notes located nearby. I consider this more as an engraving error than a future request. This shouldn't happen.
https://github.com/musescore/MuseScore/assets/134041121/4a829919-b447-4df0-9fe4-2db91fcd52f6
Problem to be solved
Firstly, removing the glissando line from a narrow space will save horizontal space and make it easier to read in places too thickened by notation, which is sometimes very important when writing scores. At the same time, the visibility of the clarifying text for the glissando line must be ensured, which does not currently work in Musescore if the line is too short for text to be displayed above it. This shouldn't happen. If the line is short and there is no space for text, then this line should be moved (automatically), and the text should be able to be displayed in any case.
Secondly, the ability to enter clarifying text for the glissando line in 2 lines will allow you to evenly distribute the text in order to make it easier to read. You should not put all the words on one line, especially when this line is not long.
And finally, thirdly. The wide area of the glissando line capture makes it very difficult for me (and I think not only for me) to write the score. I have to constantly move this glissando away from the notes, and then put it back in place again. It's very exhausting. The glissando line capture area shouldn't be that huge. @oktophonie, please deal with this, it's very stressful.
Prior art
No response
Additional context
No response
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
Start by reproducing the reported narrow-spacing, two-line clarifying-text, and oversized-capture-area cases in MuseScore. Inspect the glissando properties and engraving/editing behavior; done means automatic placement preserves readable text, supports two lines, and no longer blocks nearby notes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100