musescore / musescore/MuseScore

Better naming for elements saved as custom palette elements

Open
#34,514 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community P3 UX/interaction
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)

Description with steps to reproduce
  1. Put an accidental/dynamics to a note. Leave it as it and do not edit it in any way.
  2. Ctrl+Shift drag to palette
  3. Repeat step 2 will create many "custom palette element" entries named Accidental/Dynamic. All addition entries are named the same.

Note that formatting is recorded in the UI icon in palette. But reapplying to a note gives the default formatting.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/714522d2-80c5-4e2e-ab66-ddc40df50941

In which versions of MuseScore Studio is this issue present?

Both latest 4.7 nightly and lastest main nightly

Regression

Appears since MuseScore 3

Operating system

Win10

Additional context

I understand that such design allows storing user formats and edits. But at the moment it doesn't seem to be well implemented. Also, the name of the custom palette elements are also quite confusing. Personally I would expect sth like "Double Flat (1)"

Checklist
  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

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

Reproduce the custom-palette workflow with an accidental or dynamic: Ctrl+Shift-drag the same element repeatedly and reapply a saved entry. Trace the custom palette element handling and its naming and formatting behavior; done means entries have distinguishable names and reapplying one preserves its recorded formatting.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.