Pedaling Marks Are Incorrectly Placed

[Fourniture]

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

1. Create Organ Articulation Palette
2. Add any marking

Expected Behavior: The marking appears either above the staff (for right foot markings) or below (for left foot).
Actual Behavior: The marking is placed on top of the note to which it is attached and must be dragged manually.
In addition: The markings cannot be repositioned with the arrow keys; they must be dragged. However, the arrow keys work on every other articulation.

Supporting files, videos and screenshots

Untitled.video.-.Made.with.Clipchamp.4.mp4

Offertory.zip

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.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

Windows 11

Additional context

Yes, heel and toe organ markings are not, strictly speaking, articulations. However, I would expect to interact with them the same way. (Fingering numbers can also be moved using the arrow keys.)

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

[MarcSabatella]

This isn't really a bug - organ markings simply aren't supported yet as native elements. So, they are added as symbols only, and there is no automatic positioning algorithm for symbols since MuyseScore has no concept of what correct positioning should be for sybols that are not native elements. It is of course a valid feature request to add support for organ pedal marks as native elements.

To position symbols via keyboard, first put them into Edit mode (double-click or F2). It's also a valid feature request to consider making the cursor keys active directly for symbols.