dragging key sig off the palette removes it for good!

• Dec 24, 2022 - 23:10
Reported version
4.x-dev
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Once
Status
needs info
Regression
No
Workaround
No
Project
MuseScore

Version: OS: macOS 13.1, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-223472200, revision: 5485621

1) Drag key of 3 flats onto a staff
2) Go back to the palette
3) That key is now missing as a tile

The only other thing I did was undo the change, because it modified all my accidentals, which was not my intent. But then I decided it would be fine, and I would fix the accidentals by hand. But lo, the palette was no longer available as an option.

Closing the score and re-opening it doesn't bring the tile back, but closing MS and relaunching it does.

Untitled 2.png

Comments

• Dec 25, 2022 - 20:38

I also cannot reproduce it now.

I do see that dragging a key signature tile off the palette first starts moving tiles around within the palette, and I'm able to get it temporarily to the place where the previous square appears blank, but only until I move the tile further away, in which case the other tiles slide to fill the void on the palette.

I wonder if the redraw of the palette is going into the Undo stack? Then when I did an undo of the placement of the bbb onto the staff, the stack popped that event and left the palette with the void? Maybe one more Undo would have put the palette back to its original condition? I don't know.

Reply

• Dec 27, 2022 - 04:47

This has been an ongoing issue for years, seems to happen randomly but I'm guessing is somehow timing-related. Anyhow, it fixes itself on changes of workspace as well as restart of MuseScore.

There is no undo stack per see relating to the drag operation - what you are seeing is the palette interpreting your drag as an attempt to customize the palette, which is normally the only reason for dragging in the palette. Only when your mouse cursor leaves the palette can MuseScore conclude you are actually attempting to add the element to your score, so it then switches itself into that mode and attempts to put the palette back the way it was. It's still not clear why this last bit sometimes goes wrong.

Reply