Offsets of score elements added to palette should be ignored when displaying the palette

• Mar 29, 2021 - 21:13
Reported version
Graphical (UI)
S3 - Major

Version 3.6.2 / Windows 10

The title says it all.

For explanation and details, see some examples:

(and I am sure they are some other related posts on the forums)


Title Adding an existing score element to a palette with Ctrl/Shift/drag sometimes goes wrong, the added element being invisible. Offsets of score elements added to palette should be ignored when displaying the palette
Type Functional Graphical (UI)
Workaround No Yes

I assume you mean, the specific case of an offset that was applied to the element before adding to the palette. I've changed the title accordingly. If there is some other case you have in mind, it should probably be a separate issue.

I don't understand your reasoning. With versions 2 (and some versions 3), I never thought to check in the Inspector if the offsets were 0 or not, voluntarily or not. It didn't matter.
If this is something of a new feature, was it intended, assumed, announced and documented? Not that I know of.

Whether with these "former" versions the element/symbol was moved on the score (probably, otherwise many hit the notehead, for example) or not, the element/symbol always appeared in the palette. No one wondered if it could be otherwise!

Now, that these added elements could sometimes appear, sometimes not, without any consistency and without the user being able to predict and understand what might happen is nonsense. That's my only point. But I guess the new title addresses this issue.

To be honest I don't know. But I don't know what "reasoning" you mean. I agree it's something that should be revised. I merely changed the title to be more descriptive of the specific trigger for the issue.

MuseScore 2 didn't have this issue, but to me it had a worse one - because the offset wasn't remembered, it was impossible to add an element to the palette in a way that would reapply the same offset when using that. This is a very useful feature in MsueScore 3, when it works. It seems it only works with certain element types but not others, which is a shame.

To me, ideal would be if the palette remembered the offset and reapplied when adding from the palette - which MuseScore 2 didn't do - but didn't display the element with offset in the palette.