musescore / musescore/MuseScore
Double click/shortcut to edit text in text lines
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
Allow the user to double-click on any line (or use the editing shortcut - usually F2 on Windows) with associated text as a shortcut to directly edit the text, instead of going to the Properties panel and switching to the text tab.
The edited field should be the one clicked on or highlighted when pressing the shortcut - for instance if a line goes onto a new system and the user directly edits the text on the new system, it should update that field, rather than the Beginning text.
The text entry fields in the Properties panel should remain available, as they provide a way to edit all the parts of the text, such as when continuing on a new system, in one place without such features being currently present in the score.
Problem to be solved
Staff/system text, etc. is an editable object in the score, and can be double-clicked or edited with the shortcut key to change the text. Text lines look similar, though with their associated line, but behave completely differently. Instead of direct editing, the object must be selected, then in the Properties panel, the user has to change to the Text tab and edit there. It would be intuitive for new users to be able to directly edit this text in the score, without having to go to the Properties panel, which takes more clicks and takes the user's focus away from editing.
Prior art
Most text in Sibelius is directly editable in the score, without needing to go to properties.
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
Start by tracing how text-line objects handle double-clicks and keyboard shortcuts, then compare that path with direct editing for staff or system text. Confirm which text field was clicked or highlighted, preserve the Properties-panel editing path, and verify that double-click and the usual F2 shortcut edit the selected field in the score.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100