musescore / musescore/MuseScore
Text created in a measure isn't selectable when put into a frame, with autoplace off.
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
UX/Interaction bug (incorrect behaviour)
Bug description
To add more context to the title, this is any form of text that wasn't created using the right-click on frame>"add" method. This is all forms of text created/put into a measure/note/rest. A similar issue also occurs when you put text in any layout break. I understand that this is a duplicate of other existing issues, so one unique thing that I'll add is that an easy fix for this is to just make the default "mode" of frames and layout breaks be on "to back". Like how in the Properties tab of a frame/layout break, you can go to "appearance" and select "to back" under Arrange. That makes the text selectable like how it was in MU3. That seems like it would be the easiest fix to this.
Steps to reproduce
- Add text onto a measure.
- Turn off auto-place for that text.
- Move it into a frame.
- Text becomes no longer selectable.
Screenshots/Screen recordings
No response
MuseScore Version
4.2.1
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
Windows 11
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 selection failure in MuseScore 4.2.1 using text placed in a measure, then moved into a frame with auto-place disabled. Compare selection behavior for frames and layout breaks, including the suggested “to back” appearance setting. Done means the text remains selectable after being moved into a frame.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100