Add a "selection mode" tool to the toolbar.

[kbloom]

Resolves: #27513

It feels weird to switch back to selection mode by going to the toolbar and clicking on a note input mode to disable it. Adding a "Selection Mode" button that switches to selection mode makes the UI of these buttons more similar to how tool buttons behave in other applications (for example most graphics programs).

Some unfinished bits that I need help with:

• It would be nice if the Select button would remain highlighted once clicked, similar to how the note input buttons do. I wasn't sure how to do that.
• It feels weird to add an icon by editing a binary font file in FontForge, instead of creating a separate, reviewable file (such as an SVG) for the icon. (And what happen if my addition conflicted with someone else's changes to the font file.) Did I do that right?

• I signed the CLA
• The title of the PR describes the problem it addresses
• Each commit's message describes its purpose and effects, and references the issue it resolves
• If changes are extensive, there is a sequence of easily reviewable commits
• The code in the PR follows the coding rules
• There are no unnecessary changes
• The code compiles and runs on my machine, preferably after each commit individually
• I created a unit test or vtest to verify the changes I made (if applicable)

[bkunda]

As I mentioned in my comment here, we do not plan to add any additional modes to differentiate selection vs. note input functionalities at this time.

We also will not be introducing new functionality with the intention of later replacing it (as was suggested in this comment). This just creates technical and design debt that we have to deal with later on. It also establishes new user expectations that then have to be changed.

There are plenty of other available projects (see here), so if you're interested in contributing then please look there first and discuss your intention with the internal team before submitting a PR.

[kbloom]

This doesn't introduce an additional mode. The mode is already there. It introduces a button that makes it more intuitive to enter the existing mode. It's very common for graphics software to have this button, and it's also very common for other notation software to have this button.

…

On Wed, May 28, 2025, 5:33 AM bkunda ***@***.***> wrote: *bkunda* left a comment (musescore/MuseScore#28115) <#28115 (comment)> As I mentioned in my comment here <#27513 (comment)>, we do not plan to add any additional modes to differentiate selection vs. note input functionalities at this time. We also will not be introducing new functionality with the intention of later replacing it (as was suggested in this comment <#27513 (comment)>). This just creates technical and design debt that we have to deal with later on. It also establishes new user expectations that then have to be changed. There are plenty of other available projects (see here <https://github.com/orgs/musescore/projects/30>), so if you're interested in contributing then please look there first and discuss your intention with the internal team before submitting a PR. — Reply to this email directly, view it on GitHub <#28115 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAANXXKRDFKJDASK55XWQXT3AV7F7AVCNFSM6AAAAAB5WLWROCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJVGYZTMOBRHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[kbloom]

Anyhow, this is an implementation. Try it out and see whether it's an improvement.

…

On Wed, May 28, 2025, 6:28 AM Ken Bloom ***@***.***> wrote: This doesn't introduce an additional mode. The mode is already there. It introduces a button that makes it more intuitive to enter the existing mode. It's very common for graphics software to have this button, and it's also very common for other notation software to have this button. On Wed, May 28, 2025, 5:33 AM bkunda ***@***.***> wrote: > *bkunda* left a comment (musescore/MuseScore#28115) > <#28115 (comment)> > > As I mentioned in my comment here > <#27513 (comment)>, > we do not plan to add any additional modes to differentiate selection vs. > note input functionalities at this time. > > We also will not be introducing new functionality with the intention of > later replacing it (as was suggested in this comment > <#27513 (comment)>). > This just creates technical and design debt that we have to deal with later > on. It also establishes new user expectations that then have to be changed. > > There are plenty of other available projects (see here > <https://github.com/orgs/musescore/projects/30>), so if you're > interested in contributing then please look there first and discuss your > intention with the internal team before submitting a PR. > > — > Reply to this email directly, view it on GitHub > <#28115 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAANXXKRDFKJDASK55XWQXT3AV7F7AVCNFSM6AAAAAB5WLWROCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMJVGYZTMOBRHA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >