musescore / musescore/MuseScore

Thoughts on making palette insertion better

Open
#24,469 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

To make the insertion of palette items more quick I suggest:

  1. Possibility to define shortcut to highlight directly the palette elements.
  2. Once the palettes are highlighted and navigable, when a specific palette is selected, elements should be given a specific key as a shortcut, without having to navigate the palette with arrow keys. See image.
    Screenshot 2024-09-04 alle 14 44 17
Problem to be solved

A the present moment, inserting elements from the palettes very time-waisting: you need to either a) use the mouse or b) navigate UI elements with TAB, highlight the palette or navigate through palettes with arrow keys and then navigate through the elements of the palette with the arrow keys again; if the element is the last of the list, it will tale much time.

With a better way to insert palette items, the workflow will improve tremendously.

Prior art

No response

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

The issue does not name any files, tests, or entry points. Start by locating the desktop palette insertion and keyboard-navigation UI, then clarify the shortcut and selection behavior with maintainers. Done means palette items can be reached and inserted through the proposed keyboard workflow without repeated arrow-key navigation.

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
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.