musescore / musescore/MuseScore

Double-clicking to edit text should place the cursor in a consistent location.

Open
#34,626 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P3
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

When you double-click a piece of text to edit it, the cursor appears at a different spot each time (generally close to where you have actually clicked). This can be inefficient because you're never sure where the cursor is going to be. It would be nice to have the cursor appear in a consistent spot, either at the beginning or the end of the text string.

Problem to be solved

It's just more reliable if you know where to expect the cursor to be each time. It is difficult to be precise enough to click in the exact spot you need, plus having to be that precise takes more time.

https://github.com/user-attachments/assets/3915cb71-c22f-46f1-b0e0-38921e24ba41

Prior art

Sibelius always places the cursor at the end of the text, regardless of where you have double-clicked.

https://github.com/user-attachments/assets/802bea0c-a083-4d43-b81e-bfb9ad395c42

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the double-click text-editing behavior in MuseScore and trace the desktop text-editing interaction from there. Confirm whether the intended behavior is to place the cursor at the beginning or end of the text, then verify that repeated double-clicks consistently use that location.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.