musescore / musescore/MuseScore

After adding a new dynamic, hide the dynamic picker popup

Open
#28,408 4 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Description

Solution to implement

Agreed upon in comments below

New rules for hiding the popup immediately after creating a dynamic:

  • If you add a dynamic via palettes, do not show the popup
  • If you add a dynamic via Cmd + D, then click a dynamic in the popup, hide the popup after selecting one
  • If you add a dynamic via Cmd + D, then type in a dynamic (i.e. f), hitting 'Esc' should both confirm the dynamic and close the popup

Original issue report

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

On scores with multiple staves, the dynamics popup blocks the staff immediately below the staff being edited. This is especially unhelpful when the staff below needs to be at a different dynamic than the one above it; I have to click away from the dynamics popup before entering another dynamic.

I suggest that the dynamics popup, while very useful, is unnecessary when a dynamic is first added. (After all, I just added the dynamic I needed.) The popup should only appear when the dynamic is selected after this.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/60bf076c-a577-4938-bf16-5d39b35e355b

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: github-musescore-musescore-ac9d3bc

Regression

No.

Operating system

Windows 11

Additional context

This happens at nearly any zoom level.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.