musescore / musescore/MuseScore

[MU4 Issue] Palette properties become frozen for previously-opened palettes when adding a new palette

Open
#10,539 2 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug
Please see this video:

https://user-images.githubusercontent.com/86290556/153591397-def6fbfa-8039-4690-9d60-1db7fab20a07.mov

Expected behavior
Changes to palette properties should work for all palettes, regardless of whether a new palette has been added

Platform information

  • MacOS 12.1 (M1)
  • Windows 11

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.